Llm wiki agent memory bridge
Skill po4yka/llm-wiki-skills/skills/llm-wiki-agent-memory-bridge
Portable Agent Skills for building, operating, evaluating, and governing LLM-Wiki knowledge systems.
npx -y skills add po4yka/llm-wiki-skills --skill llm-wiki-agent-memory-bridgeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Decide what belongs in LLM-Wiki versus agent memory, AGENTS.md, CLAUDE.md, Auto Memory, Codex project memory, or other runtime memories. Use when instruction files are bloated, domain facts live in agent memory, or the user wants clean memory boundaries.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.3 KB, as published. Nobody here has run it
LLM-Wiki Agent Memory Bridge
Goal
Separate durable domain knowledge from runtime/project memory so agents load the right context at the right time.
When to use
AGENTS.md/CLAUDE.mdhas grown large because domain facts were pasted into instructions instead of the wiki.- A wiki page holds procedural agent prompts that belong in a Skill, not domain knowledge.
- Agent memory (Auto Memory, Codex project memory) duplicates or has drifted from existing wiki pages.
- You need to decide where a new piece of knowledge belongs: Skill, instruction file, or wiki.
- Onboarding a new agent (Claude Code, Codex, Cursor, OpenCode) to a project and need to map its existing memory surfaces first.
Inputs
AGENTS.md,CLAUDE.md, project memory files, agent settings.- Existing wiki/vault.
- Target agents: Claude Code, Codex, Cursor, OpenCode, etc.
- Desired mode: audit, plan, or apply.
Procedure
1. Inventory memory surfaces
Find:
- instruction files;
- agent memory files;
- skills;
- wiki pages;
- query logs;
- project docs;
- hidden or generated memory directories.
2. Classify memory items
Use this routing:
| Content | Best home |
|---|---|
| stable procedures | Agent Skill |
| project conventions | AGENTS.md or CLAUDE.md pointer |
| domain facts | LLM-Wiki page with provenance |
| source-backed claims | wiki/sources, wiki/concepts, wiki/entities |
| user preferences | agent/user memory, not public wiki |
| temporary task state | current session or task log |
| sensitive facts | restricted wiki or local-only memory |
3. Detect bloat and drift
Flag:
- giant instruction files full of domain knowledge;
- skills containing volatile facts;
- agent memory duplicating wiki pages;
- wiki pages containing procedural prompts;
- missing pointers from instruction files to wiki index;
- volatile facts (pricing, release notes, maintenance status) embedded directly in a skill or instruction file instead of a wiki page whose claims get re-verified against fresh sources before reuse.
4. Propose moves
Create a migration table:
| Item | Current location | Proposed home | Reason | Risk |
|---|---|---|---|---|
5. Apply safe pointer pattern
Keep instruction files short. Replace long domain dumps with pointers such as:
For domain knowledge, read `wiki/index.md` first and then relevant linked pages.
Output
## Memory boundary summary
## Memory surfaces found
## Misplaced content
## Proposed moves
## Instruction-file pointer updates
## Risks
Safety gates
- Do not move user preferences into a shared wiki without approval.
- Do not delete memory content during migration; archive or link it.
- Do not hide domain facts in skills.
- Do not leave instruction files without pointers to the wiki.