Run any Skill in Manus with one click

audit

Stars5

Forks1

UpdatedApril 14, 2026 at 22:54

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

seanbonner

seanbonner/Grimoire

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

File ClerksOffice and Administrative Support Occupations·SOC 43-4071

File Explorer

2 files

SKILL.md

readonly

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.

audit

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.

What to look for

Contradictions between pages. Two pages making opposing claims, or a source page whose claim isn't reflected on the concept page that cites it.
Orphan pages. Pages with no inbound links from anywhere (not from 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.
Concepts mentioned but not pages. Recurring [[wikilinks]] (or recurring inline mentions) of a concept that has no page yet. These are concept-hub candidates for the next bind.
Stale claims. A page making a claim a newer source has superseded or contradicted, where the page hasn't been updated.
Weak cross-references. Pages that should be linked together (clear thematic overlap) but aren't.
Suggested topics. Gaps where the existing material implies an investigation worth running.

Output

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).

More from this repository

same repository

bind

seanbonner/Grimoire

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.

2026-05-055

divine

seanbonner/Grimoire

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.

2026-05-055

inscribe

seanbonner/Grimoire

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.

2026-05-055

consult

seanbonner/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.

2026-04-165

illuminate

seanbonner/Grimoire

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).

2026-04-145

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.

audit

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.

What to look for

Contradictions between pages. Two pages making opposing claims, or a source page whose claim isn't reflected on the concept page that cites it.
Orphan pages. Pages with no inbound links from anywhere (not from 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.
Concepts mentioned but not pages. Recurring [[wikilinks]] (or recurring inline mentions) of a concept that has no page yet. These are concept-hub candidates for the next bind.
Stale claims. A page making a claim a newer source has superseded or contradicted, where the page hasn't been updated.
Weak cross-references. Pages that should be linked together (clear thematic overlap) but aren't.
Suggested topics. Gaps where the existing material implies an investigation worth running.

Output

## 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).