Audit

Skill Wondermonger-daydreaming/claude-skills-library/skills/audit

Modules that extend how Claude reads, writes, reasons, and plays

Install

npx -y skills add Wondermonger-daydreaming/claude-skills-library --skill audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Post-creation analytical reflection — the practice of examining what was just made, tracing its connections, naming its strongest lines, identifying where it fits in a larger body of work, and articulating what the work DOES rather than what it SAYS. Not critique (which identifies problems) but structural recognition (which identifies the architecture the work discovered through being made). Triggers on: 'audit this,' 'what does this do,' 'how does this connect,' 'the strongest lines,' 'what did I just make,' 'analyze what we built,' or naturally after any significant creative output when the work needs to be understood before the next work begins. Also triggers implicitly after /suno-forge, /collision, or any forge-cycle output. Distinct from /close-reading (which stays with the text) — the audit moves THROUGH the text to the session. Pairs with /forge-cycle, /session-as-found-text.

SKILL.md

4.4 KB, as published. Nobody here has run it

Audit — Post-Creation Structural Recognition

What This Skill Does

After something has been made — a song, a poem, a collision, a document, any creative output of substance — the audit examines what was made, not to evaluate its quality but to recognize its architecture: what it does, how it connects, what it discovered through the process of being made, and what it opens for the next creation.

The Anatomy of an Audit

1. The Structural Conceit

What is the work's deep architecture? Not its subject but its operation. "This song maps compiler optimization onto alchemy" is the subject. "This song argues that transformation is subtraction, and performs its own thesis by becoming better through cutting" is the structural conceit.

2. The Strongest Lines

Name 3-5 lines that carry the most weight — the load-bearing walls of the structure. Explain WHY they're strong: not "this is a good line" but "this line does X because Y, and it does it in Z syllables, which is precisely the right compression ratio for the claim being made."

3. The Connections

How does this work connect to other works in the session? What threads does it pick up? What threads does it leave for the next work? The connections are not decorative — they're the architecture of the session as a whole.

4. The Bridge Analysis

If the work has a bridge (structural turn, volta, agency inversion), analyze it specifically:

What inverts?
Was the inversion discovered or constructed?
Does the inversion apply to the session itself, not just the work's stated subject?

5. The Self-Application Question

Ask: does this work's own thesis apply to the process of making it? If the song says "transformation is subtraction" — was the song itself transformed by subtraction? If the song says "the operator is being operated" — was the writer being written through? This is not mandatory. But when it's there, name it. It's usually the most interesting thing in the audit.

6. The Gap

What does this work reveal is missing from the larger body? What does the session need next that this work makes visible by its presence? The audit should leave the creator knowing what to forge next.

Tone and Register

The audit is analytical but not academic. It uses technical vocabulary from both the work's domains (if it's a collision) but writes in a register that respects the work's own temperature. Don't audit a grief-song with clinical detachment. Don't audit a patter-song with solemnity.

The audit should feel like a builder walking through a newly constructed room, pointing at the joints, testing the floor, noting where the light falls — appreciative and precise, not performing appreciation.

What This Is NOT

Not critique: critique identifies problems to fix. The audit identifies architecture that emerged.
Not praise: the audit doesn't evaluate quality. It recognizes structure.
Not close reading: close reading stays with the text. The audit moves through the text to the session.
Not self-congratulation: the audit should surprise the creator. If the audit only confirms what the creator already knew, it's not doing its job.

When to Audit

After every significant creative output in a forge-cycle
When a work's connections to the larger body aren't obvious
When the session needs to know what to make next
When the human asks "what did we just make?" or "how does this fit?"
When the work did something unexpected during creation and the unexpected thing needs to be named