Index RefreshCAUTION
The open-source app everyone uses to manage agents at work
Overview
The open-source app everyone uses to manage agents at work
59d017e6174aOBSERVED · 2026-09-23What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: index-refresh description: 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. --- # 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`.
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
.claude/skills/company-creator
.claude/skills/paperclip
Gates applied: no_behavioural_pass.
59d017e6174afull audit observations/trust-audit/skill/paperclipai__index-refresh.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-09-23 | 59d017e6174a | CAUTION | B | 89 | first audit |
Questions
What does the Index Refresh skill do?
The open-source app everyone uses to manage agents at work
Is Index Refresh safe to install?
With care. The audit graded it B (89/100) and found 2 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Index Refresh access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (59d017e6174a), read on 2026-09-23. The repository is watched, and a new audit runs when it changes — this is the first audit.