wiki
Skill8 starsChanged 6 months agoMITView on GitHub
Use when the user wants to ingest sources into the wiki, query existing knowledge, or lint the knowledge base for issues. Manages a persistent, interlinked knowledge base (LLM Wiki) with three operations: ingest, query, lint.
43 other projects use a version of this.
Adopted by
Most recently taken up by
- tboome33/obsidian-mcp-routertheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- skillberry-ai/cap-evolvetheir own version, first seen Nov 8, 2026
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
- SethGammon/Citadeltheir own version, first seen Nov 4, 2026
- zlatko-lakisic/agent-cooptheir own version, first seen Nov 1, 2026
Used with
Projects with it also use ai-slop-cleaner, ralplan and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Jurel89Skillai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Also in 4 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 4 projects that use this
Yeachan-HeoSkillultragoal
Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.
Also in 3 projects that use this
woosikkimSkilldeepinit
Generate hierarchical AGENTS.md codebase maps for agent context
Also in 3 projects that use this
ibahgatSkillhud
Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.
Also in 3 projects that use this
klauswgSkilldeep-interview
在明确批准执行之前,通过数学化歧义门控进行苏格拉底式深度访谈
Also in 4 projects that use this
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- AgriciDaniel/claude-obsidian★ 16ksame name
- SethGammon/Citadel★ 927same name
- saltmd/salt.md★ 178same name
- ekadetov/llm-wiki★ 108same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- skillberry-ai/cap-evolve★ 70same name
- WALKERKILLER/Look-Tongji-Notes★ 53same name
33 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- memory/CLAUDE.mdCLAUDE.md
- claude-md-templateSkill
- daily-briefingSkill
- google-workspace-cliSkill
- memory-claude-md-syncSkill
- task-managementSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 5 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Read the source document fully.
- Very specific: line 44
Update existing project and concept pages with new information from the source.
- Distinctive: line 46
Add new pages to the appropriate section (Projects, Concepts, Preferences)
- Distinctive: line 47
Update one-line summaries if they've become stale
- Very specific: line 48
Delete the source file from sources/ — it has been fully processed.
- Very specific: line 51
Never modify files in sources/.
- Very specific: line 54
Every new page must be added to memory/CLAUDE.md.
- Very specific: line 55
Delete each source file after processing — sources/ should be empty when all ingestion is done.
- Very specific: line 56
Use relative links between wiki pages (they're all siblings in memory/).
- Very specific: line 65
Read memory/CLAUDE.md to identify relevant pages.
- Very specific: line 68
If the answer represents a valuable synthesis (comparison, analysis, connection), offer to file it as a new wiki page of type synthesis.
- Distinctive: line 71
Always cite which wiki pages informed the answer.
- Distinctive: line 72
If the wiki doesn't contain enough information, say so and suggest sources to ingest.
“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LLM Wiki
A persistent, compounding knowledge base. The LLM writes and maintains the wiki; {{NAME}} curates sources, directs analysis, and asks questions.
Architecture
Three layers:
- Sources (
sources/) — raw, immutable input documents (transcripts, articles, PDFs). Never modified by the LLM. - Wiki (
memory/) — flat directory of LLM-generated markdown pages. All pages are siblings.memory/CLAUDE.mdis the navigation hub. - Schema (
CLAUDE.md+ this skill) — governs structure and operations.
Operations
Ingest
Process a raw source from sources/ into wiki pages. Invoked via the /project:wiki-ingest command.
Input: path to a source file.
Steps:
- Read the source document fully.
- Identify key information:
- Decisions made and their rationale
- Action items and who owns them
- People mentioned (names, roles, context) — capture on the relevant project/concept page, never as standalone pages
- Concepts/themes discussed
- Contradictions with existing wiki content
- For each new concept/theme that deserves its own page, create one:
--- type: concept name: Concept Name first_seen: YYYY-MM-DD --- - Update existing project and concept pages with new information from the source. Add cross-references (
[link text](other-page.md)) between related pages. - Update
memory/CLAUDE.md:- Add new pages to the appropriate section (Projects, Concepts, Preferences)
- Update one-line summaries if they've become stale
- Delete the source file from
sources/— it has been fully processed.
Rules:
- Never modify files in
sources/. They are immutable. - Never create person pages. People are documented inline on the project or concept pages where they are relevant (e.g., a collaborators table or section).
- One page per entity (project, concept). If a page already exists, update it — don't create a duplicate.
- Every new page must be added to
memory/CLAUDE.md. - Delete each source file after processing —
sources/should be empty when all ingestion is done. - Use relative links between wiki pages (they're all siblings in
memory/). - Frontmatter
typefield is required on all pages:project,concept,preference, orsynthesis.
Query
Answer questions using the wiki as the primary knowledge source.
Steps:
- Read
memory/CLAUDE.mdto identify relevant pages. - Read those pages.
- Synthesize an answer with citations to specific wiki pages.
- If the answer represents a valuable synthesis (comparison, analysis, connection), offer to file it as a new wiki page of type
synthesis.
Rules:
- Always cite which wiki pages informed the answer.
- If the wiki doesn't contain enough information, say so and suggest sources to ingest.
Lint
Health-check the wiki. Run periodically or on request.
Checks:
- Orphan pages — files in
memory/not listed inmemory/CLAUDE.md. - Broken links — references to pages that don't exist.
- Stale content — pages not updated in 30+ days that reference active projects.
- Missing cross-references — pages that mention entities with their own page but don't link to them.
- Contradictions — claims in one page that conflict with another.
- Missing pages — entities mentioned across multiple pages that lack their own dedicated page.
- Index drift — one-line summaries in
memory/CLAUDE.mdthat no longer match page content.
Output: a report listing issues found and suggested fixes. Apply fixes only with confirmation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

