How to use the index-refresh agent skill for LLM Wiki

What is an agent skill and what does index-refresh do?

An agent skill is a folder containing a SKILL.md file: written instructions that an AI agent reads when a task matches the skill's description. This one is named index-refresh and is triggered when an LLM Wiki operation issue requests an index refresh.

When it runs, the agent reads wiki/index.md, walks the wiki's directory tree, and adds links to pages that exist but are missing from the index. It removes entries for pages that have been deleted and writes a one-line summary for each entry, taken from the page's own first paragraph or title. It then records counts in wiki/log.md. The skill is designed not to edit the content of any page.

• Adds index entries for pages on disk that are missing from the index.
• Removes index entries whose page no longer exists.
• Groups entries by category: sources, projects, entities, concepts and synthesis, plus any custom categories the wiki defines.
• Appends a dated entry with counts to wiki/log.md as an audit trail.

Install the index-refresh skill

Download the ZIP from the skill's page in this directory and unzip it. To make the skill available to Claude Code across your projects, place the unzipped folder in ~/.claude/skills/. To scope it to a single project, place it in that project's .claude/skills/ folder instead.

If you use the Claude apps, you can upload the skill instead. Open Settings, go to Capabilities, then Skills, and upload the skill there.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills

Set up the environment the skill needs

The skill depends on the Paperclip LLM Wiki plugin environment. It expects three tools to be available: wiki_search, wiki_read_page and wiki_write_page. Without them, the agent cannot read the wiki or write the index.

The skill also needs an operation issue with operationType set to "index". That issue must supply the wikiId and spaceSlug of the target space. The skill refreshes only that space unless the issue explicitly asks for a multi-space sweep.

• Paperclip LLM Wiki plugin environment providing wiki_search, wiki_read_page and wiki_write_page
• An operation issue with operationType "index"
• wikiId and spaceSlug in the operation issue

How to trigger the skill with a natural request

The skill is triggered by context rather than a fixed command. The description tells the agent to use it when an LLM Wiki operation issue requests an index refresh. In practice, you create or point the agent to an operation issue of type index that names the wiki and space, and the agent matches the request to this skill.

The index-refresh routine title is also accepted as a trigger, so asking the agent to run the index-refresh routine for a given space is a reasonable phrasing. Check that the issue includes the wikiId and spaceSlug, because the skill will not proceed without them.

• "Run the index refresh for the research wiki, space marketing." (include the issue's wikiId and spaceSlug)
• "Process the index operation issue for this wiki and rebuild the index."
• "Run the index-refresh routine for space docs and log the counts."

What the skill will not do

The skill is narrow by design. It does not change page content, does not resolve contradictions, does not fix broken links and does not fill concept gaps. It also does not write a summary that the page does not support. If a page has no clear first paragraph, the skill flags it for the separate wiki-lint step.

If you need broken links fixed or new content written, use wiki-lint or another workflow, not index-refresh.

• Does not edit page bodies or any file under raw/.
• Does not fix broken links or resolve contradictions.
• Does not write summaries that the page itself does not support.

Check the result

After a run, review wiki/index.md and the new entry at the end of wiki/log.md. The skill's verification checklist requires that the index matches the actual contents of wiki/, that each line has the form shown below, and that custom category sections are kept. The log entry must exist even when the counts are zero.

• Index lines follow the form - [[path]] — summary.
• Log entry header shows added=N removed=M.
• Log names the operation issue identifier.