メニュー
Use when the user asks to audit, lint, or check the wiki — surfaces contradictions, orphans, mentioned-but-missing concepts, stale claims, and weak cross-references. Reports only; does not write except for unambiguous typos and broken links.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks for a weekly review, reflection, or deep pass — updates concept and entity pages with material inscribed since the last bind, creates hubs when warranted, runs the batched Shelves cross-check, and flags synthesis candidates for the user to draft with divine.
Use when the user asks for a synthesis, deeper analysis, or picks up a candidate flagged by bind — drafts a synthesis essay under scrolls/synthesis/ that connects concepts, entities, and sources into a single cross-cutting argument. Propose-before-doing.
Use when the user asks to process the desk, ingest material, or words to that effect — classifies each item in desk/ and dispatches to the Shelves pipeline (catalog items) or the Scrolls pipeline (everything else). The only inbox entry point in Grimoire.
Use when the user asks a substantive question the wiki should be the primary source for — reads the index, pulls relevant pages, synthesizes an answer with wikilinks back to sources, and offers to save reusable answers as reports.
Use when the user asks to localize images, pull images local, or roughly monthly — sweeps the corpus for remote image URLs that will rot, downloads them to raw/assets/, and rewrites the markdown references to local relative paths. The name is borrowed from illuminated manuscripts (images in pages).
| name | audit |
| description | Use when the user asks to audit, lint, or check the wiki — surfaces contradictions, orphans, mentioned-but-missing concepts, stale claims, and weak cross-references. Reports only; does not write except for unambiguous typos and broken links. |
This skill is written from the CLAUDE.md spec, not from a real run. After the first real audit pass, rewrite this skill from what actually happened.
Audit is a reporting operation, not a writing operation. Its job is to surface issues for the user (or for the next bind pass) to act on. Don't fix things unilaterally unless they are unambiguous typos or broken-link cleanups.
scrolls/index.md, not from any ## See also, not from any frontmatter sources: reference). Orphans aren't necessarily wrong — sometimes a page is the seed of a future cluster — but they should be visible.[[wikilinks]] (or recurring inline mentions) of a concept that has no page yet. These are concept-hub candidates for the next bind.Write the audit result as a structured report directly to the user in the conversation. If the report is substantive enough that the user will want to refer back to it, offer to save it to scrolls/reports/. Either way, append a short entry to scrolls/log.md using the canonical header format:
## YYYY-MM-DD audit — <one-line summary of what surfaced>
Body: how many issues in each category, plus any items that were unambiguous enough to fix in passing (broken links, obvious typos).