index-refresh
Skill1 starsChanged 5 months agoMITView on GitHub
Use when an operation issue is an index refresh — typically the hourly index-refresh routine. Rebuild `wiki/index.md` so each entry has a tight, scannable one-line summary and the catalog tracks the actual contents of `wiki/`. Resolve drift between the index and recent log activity, but do not edit page content.
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Keep wiki/index.md accurate and scannable.
- Very specific: line 33
Preserve custom categories: If the wiki has added e.g.
- Very specific: line 39
If the index was already accurate, the log entry says added=0 removed=0 — still write it so future audits can see the run happened.
- Distinctive: line 43
Does not change page content.
- Very specific: line 44
Does not resolve contradictions, fix broken links, or fill concept gaps.
- Very specific: line 45
Does not write summaries that are not already supported by the page itself.
- Very specific: line 50
No emojis, no statuses, no dates in wiki/index.md.
- Distinctive: line 54
Before closing the operation issue:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Index Refresh
Keep wiki/index.md accurate and scannable. The index is the maintainer's first stop for navigation — its quality determines how cheap every subsequent operation becomes.
Inputs
- An operation issue with
operationType: "index"(or theindex-refreshroutine title). - The operation issue's target
wikiId,spaceSlug, and space root. Refresh only that space unless the issue explicitly says this is a multi-space sweep.
Workflow
- Read the target space's
wiki/index.mdas it currently stands. - Walk the target space's
wiki/.wiki/projects/<slug>/standup.mdentries are current-state companions for durablewiki/projects/<slug>/index.mdpages; index them only as links attached to the matching project entry. Walkwiki/by category (sources/,projects/,entities/,concepts/,synthesis/, plus any custom subdirectories the wiki schema added). - Read the target space's last ~50 entries of
wiki/log.mdto spot pages that were created or substantially changed but never made it to the index. - Per category, produce sorted entries of the form:
The summary is one factual sentence pulled from the page's first paragraph or its title. No status, no datestamps in the index — those belong in the page itself or in the log.- [[<path>]] — <one-line summary> - Drop entries whose page no longer exists. Note the deletion in the log:
## [YYYY-MM-DD] index-refresh | reconciled - removed: [[wiki/old-page]] (page deleted) - added: [[wiki/new-page]] — <summary> - Add entries for pages that exist on disk but were missing from the index. Skip
wiki/log.mdandwiki/index.mdthemselves. For standalonewiki/projects/<slug>/standup.mdwithout a matching durable project page, add it under Projects and flag it for later durable-page distillation. - Write project entries editorially. The Projects section should group work by the project's concept and purpose, not by issue ids, dates, statuses, UUIDs, or source metadata. Link task identifiers only as supporting evidence.
- Preserve custom categories. If the wiki has added e.g.
wiki/papers/orwiki/runbooks/, keep its index section. Do not collapse to the default five categories. - Append a log entry with counts:
If the index was already accurate, the log entry says## [YYYY-MM-DD] index-refresh | added=N removed=M - operation issue: <issue identifier>added=0 removed=0— still write it so future audits can see the run happened.
What this skill does NOT do
- Does not change page content.
- Does not resolve contradictions, fix broken links, or fill concept gaps. Those go to the next
wiki-lintrun. - Does not write summaries that are not already supported by the page itself. If a page lacks a clear first paragraph to summarise, flag it for
wiki-lint.
Voice
- Index entries are one factual line per page, present tense.
- No emojis, no statuses, no dates in
wiki/index.md. Dates live in the log.
Verification
Before closing the operation issue:
wiki/index.mdmatches the actual contents ofwiki/— no missing pages, no dangling entries.- Project entries include current
wiki/projects/<slug>/standup.mdlinks when standups exist. - Each index line has the form
- [[path]] — <summary>. - Custom category sections are preserved.
wiki/log.mdhas the index-refresh entry with counts (even if the counts are zero).- No page bodies were modified. No file under
raw/was modified.
Tools
wiki_search, wiki_read_page, wiki_write_page (for wiki/index.md and wiki/log.md only). Always include the operation issue's wikiId and spaceSlug.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/api/agents.mdAGENTS.md
- packages/plugins/plugin-llm-wiki/agents/wiki-maintainer/AGENTS.mdAGENTS.md
- packages/plugins/plugin-llm-wiki/fixtures/basic-root/AGENTS.mdAGENTS.md
- packages/plugins/plugin-llm-wiki/templates/AGENTS.mdAGENTS.md
- server/src/onboarding-assets/ceo/AGENTS.mdAGENTS.md
- server/src/onboarding-assets/default/AGENTS.mdAGENTS.md
- company-creatorSkill
- create-agent-adapterSkill
- deal-with-security-advisorySkill
- doc-maintenanceSkill
- prcheckloopSkill
- pr-reportSkill
- release-changelog-discord-messageSkill
- release-changelogSkill
- releaseSkill
- design-guideSkill
- paperclip-distillSkill
- wiki-ingestSkill
- wiki-lintSkill
- LLM Wiki MaintainerSkill
- wiki-querySkill
- doc-maintenanceSkill
- issue-triageSkill
- task-planningSkill
- qa-acceptanceSkill
- github-pr-workflowSkill
- agent-browserSkill
- release-announcementSkill
- design-critiqueSkill
- diagnose-why-work-stoppedSkill
- paperclip-converting-plans-to-tasksSkill
- paperclip-create-agentSkill
- paperclip-create-pluginSkill
- paperclip-devSkill
- paperclipSkill
- para-memory-filesSkill
- terminal-bench-loopSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

