index-refresh
Helps your agent update documentation indexes. It's useful for ensuring wiki navigation and organization are always correct.
What it does
This tool organizes and updates an index (a list of pages) for a note-taking system called a Wiki. It ensures the list is always correct, reflecting existing pages and removing deleted ones.
When to use it
- ✓When the Wiki's page list is outdated.
- ✓After deleting or adding important new pages.
- ✓To ensure navigation within the Wiki is easy and fast.
Example of what to ask your AI
“Update the Wiki index so it shows all existing pages and removes those that have been deleted.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool compares the current page list with what actually exists in the Wiki. It adds new pages to the list and removes those that no longer exist, logging everything in the history.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add paperclipai/paperclip --skill index-refreshOr download just the file:
curl -L https://raw.githubusercontent.com/paperclipai/paperclip/master/packages/plugins/plugin-llm-wiki/skills/index-refresh/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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.
FAQ
Does the tool change the content of my notes?
No, it only organizes the page list (the index) and does not alter the content of your notes.
What happens if a page is deleted?
The tool removes the deleted page from the index and logs this action in the history.
Does the tool create summaries for pages?
It uses a short summary from the page itself or its title for the index. If a page lacks a clear summary, it might ask another tool for help.
Details
Original description by the author
Use when an LLM Wiki operation issue requests an index refresh. Rebuild `wiki/index.md` from the actual wiki tree, reconcile missing/deleted entries, and log counts without editing page bodies.
repo: paperclipai/paperclip
Popularity
- GitHub stars
- 103k
- Ranking position
- #369
- License
- MIT
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
delegate-work
Helps your agent delegate work to another agent. It's useful for breaking down complex tasks and tracking progress in an organized way.
paperclipai/paperclip
follow-up-results
Has your agent check results from previous work. It's useful for tracking task progress and adding human feedback.
paperclipai/paperclip
review-my-team
Helps your agent review the connected team. It's useful for getting a summary of the team, tasks, blockers, and pending approvals.
paperclipai/paperclip
paperclip-task-bridge
Has your agent create and manage tasks on another platform. It's useful for interacting with project management systems directly.
paperclipai/paperclip
Similar skills
architecture-decision-records
Has your agent record important project structure decisions. It helps to understand the reasoning behind choices and maintain a clear history of changes.
affaan-m/ECC
code-tour
Lets your agent create step-by-step code walkthroughs with exact file and line anchors. It's useful for project introductions, code explanations, or change reviews. Helps understand how a system works.
affaan-m/ECC
codebase-onboarding
Helps your agent analyze unfamiliar code and create an onboarding guide. It includes an architecture map, entry points, and conventions. Ideal for starting on a new project.
affaan-m/ECC