wiki-maintain
Skill1 starsChanged 5 months agoMITView on GitHub
Maintain the project wiki: ingest sources, promote syntheses, retract / supersede / purge sources, run audits and resolve reviews. Use when the user asks you to change the canonical knowledge base. All changes go through the wiki CLI; never edit canonical files directly.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- huxwaitt/claude-wikitheir own version, first seen Aug 17, 2026
- Oshayr/LLM-Wikitheir own version, first seen Apr 10, 2026
- AGMO-Inc/agmo-everywheretheir own version, first seen Mar 18, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Oshayr/LLM-Wiki★ 50same name
- AGMO-Inc/agmo-everywhere★ 4same name
- huxwaitt/claude-wiki★ 0same name
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 repository2 other files it gives its agents.
- wiki-masterSkill
- wiki-querySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read ../wiki-docs/CONTRACT.md, ../wiki-docs/MUTATION-CONTRACT.md, ../wiki-docs/CHEATSHEET.md before acting.
- Very specific: line 15
Use only mutation commands through the CLI.
- Distinctive: line 17
Before mutating, check for open blocking reviews whose scope intersects your target and surface them.
- Very specific: line 23
After source-affecting changes, run wiki rebuild then wiki lint, and resolve any errors.
“Common” is measured: kept by at least 6 in 10 of the 3 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 Maintain Skill
Read ../wiki-docs/CONTRACT.md, ../wiki-docs/MUTATION-CONTRACT.md, ../wiki-docs/CHEATSHEET.md before acting.
- Use only mutation commands through the CLI; never directly edit canonical
wiki state or anything under
.wiki/ops/. - Before mutating, check for open blocking reviews whose scope intersects your target and surface them.
- Respect precedence and contradiction policy: represent conflicts (dispute or
review), never silently delete a claim; recency wins only via explicit
wiki supersede. - Promote only on explicit user intent, honouring the CLI's support thresholds.
- After source-affecting changes, run
wiki rebuildthenwiki lint, and resolve any errors. - On recovery-required (exit 6), run
wiki recover --auto; for a divergent operation pick--keep-live/--restore-before/--apply-afterper user intent.
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.