agentleFS
alainatoralainator/worldcodex/.claude/skills/auditing-canon/SKILL.md

auditing-canon

Skill2 starsChanged 7 months agoMITView on GitHub

Verifies canon status, naming compliance, frontmatter completeness, writing standards, and cross-reference validity across worldbuilding files. Use when checking naming consistency, verifying frontmatter, auditing prose standards, or when user says "canon audit", "check names", "verify frontmatter", "writing standards check", or "naming audit". Does NOT check physics equations — use /auditing-physics for that.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify naming, frontmatter, writing standards, and cross-references.

    line 16
  2. Distinctive:

    Read CLAUDE.md for locked spellings, naming conventions, and writing rules.

    line 20
  3. Distinctive:

    Every file has YAML frontmatter: title, tags, status

    line 38
  4. Distinctive:

    No meta-commentary ("This section establishes...")

    line 43
  5. Distinctive:

    No narrative content in science directories

    line 44
  6. Distinctive:

    All markdown links resolve to existing files

    line 48
  7. Distinctive:

    Do NOT fix anything. Report only.

    line 59
  8. Distinctive:

    Does NOT check physics consistency or equations (use /auditing-physics).

    line 63
  9. Distinctive:

    Does NOT treat cross-civilization differences as contradictions.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Auditing Canon

Verify naming, frontmatter, writing standards, and cross-references.

Prerequisites

Read CLAUDE.md for locked spellings, naming conventions, and writing rules.

Chain of Draft Mode

Name check. Human term found. Science dir. #### VIOLATION.
Frontmatter. status field missing. #### VIOLATION.
Spelling. Variant found. #### VIOLATION: use canonical form.
Cross-ref. Link resolves. #### PASS.

Checks

Naming

  1. In-universe terminology used correctly per directory type
  2. Locked spellings match CLAUDE.md table

Frontmatter

  1. Every file has YAML frontmatter: title, tags, status
  2. Status is one of: canon, draft, needs-review, superseded

Writing Standards (science files only)

  1. Academic third-person prose throughout
  2. No meta-commentary ("This section establishes...")
  3. No narrative content in science directories
  4. Citations use consistent format with ## References section

Cross-References

  1. All markdown links resolve to existing files
  2. GLOSSARY.md entries exist for key terms

Output

  • STYLE — writing standard violation
  • META — self-referential document language
  • DRIFT — spelling or naming inconsistency
  • ORPHAN — referenced entity has no file
  • BROKEN-REF — link to nonexistent file

Do NOT fix anything. Report only.

Out of Scope

Does NOT check physics consistency or equations (use /auditing-physics). Does NOT treat cross-civilization differences as contradictions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.