wiki
Skill74 starsChanged 9 days agoMITView on GitHub
Use when the user says "wiki", "compile inbox", "update wiki", "knowledge base", "process inbox", or "add to wiki
42 other projects use a version of this.
Adopted by
Most recently taken up by
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir 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
- Lixiuxiu559/AgentForgetheir own version, first seen Nov 1, 2026
- smkg75/wikidoctheir own version, first seen Oct 25, 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 versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 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
- skillberry-ai/cap-evolve★ 69same name
- WALKERKILLER/Look-Tongji-Notes★ 53same name
- 6eanut/llm-wiki★ 43same name
32 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 repository19 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- bootSkill
- brandSkill
- catchupSkill
- contentSkill
- dailySkill
- emailSkill
- moneySkill
- oppsSkill
- outreachSkill
- projectSkill
- resumeSkill
- shipSkill
- summarySkill
- tldrSkill
- video-notesSkill
- weeklySkill
- wiki-healthSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read wiki/_index.md for existing articles.
- Distinctive: line 26
Add a backlink to the new article from every existing article that should reference it.
“Common” is measured: kept by at least 6 in 10 of the 36 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
/wiki: compile the inbox into a linked knowledge base (Karpathy's LLM-wiki pattern)
- List
inbox/. If empty, say so and stop. - Read
wiki/_index.mdfor existing articles. - For each inbox file: read it, decide its topic, then update the matching
wiki/<slug>.mdor create one:
# <Topic>
## Summary
2-3 dense sentences, tied to the user's goals in hot.md.
## Key concepts
- **Concept**: one line each
## How it connects to my work
## Related
[[slug]] | [[slug]]
## Sources
---
*Last updated: YYYY-MM-DD*- Add a backlink to the new article from every existing article that should reference it.
- Rewrite
wiki/_index.md:- [[slug]]: one-line description, alphabetical, with a "Last compiled" date. - Move processed files to
archive/raw/YYYY-MM-DD-<name>. - Report: files processed, articles created or updated, backlinks added, anything surprising.
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.

