New to Claude Skills? Learn how to install them →

paperclipai on GitHub

Index Refresh

Free

Maintain an accurate and scannable wiki index.

Get this skill

Free · Opens the source repo

What Index Refresh does

The Index Refresh skill is designed to ensure that your wiki's index file, wiki/index.md, accurately reflects the current state of your wiki tree. This is essential for maintainers, as a well-organized index enhances navigation and reduces the overhead for subsequent operations. The skill automates the process of rebuilding the index by reconciling entries based on the actual contents of the wiki, providing a clear and concise summary of each page without altering the page bodies themselves.

When invoked, the skill reads the existing index and walks through the wiki's directory structure to gather relevant entries. It compiles a list of pages, categorizing them appropriately while also identifying any missing or deleted pages. The skill ensures that only valid links are included, and it appends a log entry that summarizes the changes made during the refresh operation. This systematic approach not only keeps the index up to date but also aids in auditing and tracking the history of changes.

This skill is particularly useful for teams and individuals managing extensive wikis where content is frequently added, modified, or deleted. By automating the index refresh process, users can save time and reduce the risk of human error, ensuring that the index remains a reliable resource for navigation and reference. Whether you are a developer, project manager, or content maintainer, this skill helps maintain the integrity and usability of your wiki.

However, it is important to note that the Index Refresh skill does not modify the content of the pages themselves, resolve contradictions, or fix broken links. Its primary function is to ensure that the index accurately reflects the current state of the wiki without delving into the content quality or coherence. For those looking to enhance their wiki management practices, this skill is a valuable addition to the toolkit.

When to use it

Use this skill when there are changes in your wiki that require the index to be refreshed for accurate navigation.

When not to use it

Do not use this skill if you need to modify page content or resolve content discrepancies; it strictly focuses on index maintenance.

What you can build with it

Updating a Project Wiki

When a project team adds new documents or modifies existing ones, use the Index Refresh skill to ensure the project wiki's index reflects these changes.

Routine Wiki Maintenance

In preparation for a quarterly review, run the Index Refresh skill to ensure that all entries are current and accurately represented in the index.

After Content Deletion

If several pages have been deleted from the wiki, use this skill to reconcile the index and remove any references to those pages.

How to install Index Refresh

View source

1. Install with the skills CLI

npx skills add paperclipai/paperclip/index-refresh --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by paperclipai

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 the index-refresh routine 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

  1. Read the target space's wiki/index.md as it currently stands.
  2. Walk the target space's wiki/. wiki/projects/<slug>/standup.md entries are current-state companions for durable wiki/projects/<slug>/index.md pages; index them only as links attached to the matching project entry. Walk wiki/ by category (sources/, projects/, entities/, concepts/, synthesis/, plus any custom subdirectories the wiki schema added).
  3. Read the target space's last ~50 entries of wiki/log.md to spot pages that were created or substantially changed but never made it to the index.
  4. Per category, produce sorted entries of the form:
    - [[<path>]] — <one-line summary>
    
    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.
  5. 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>
    
  6. Add entries for pages that exist on disk but were missing from the index. Skip wiki/log.md and wiki/index.md themselves. For standalone wiki/projects/<slug>/standup.md without a matching durable project page, add it under Projects and flag it for later durable-page distillation.
  7. 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.
  8. Preserve custom categories. If the wiki has added e.g. wiki/papers/ or wiki/runbooks/, keep its index section. Do not collapse to the default five categories.
  9. Append a log entry with counts:
    ## [YYYY-MM-DD] index-refresh | added=N removed=M
    - operation issue: <issue identifier>
    
    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.

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-lint run.
  • 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.md matches the actual contents of wiki/ — no missing pages, no dangling entries.
  • Project entries include current wiki/projects/<slug>/standup.md links when standups exist.
  • Each index line has the form - [[path]] — <summary>.
  • Custom category sections are preserved.
  • wiki/log.md has 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.

Frequently asked questions about Index Refresh

Similar skills