continuity-audit
Skill1 starsChanged 5 months agoMITView on GitHub
Perform a read-only, evidence-based audit of Markdown story artifacts for fact-source, revision, and continuity risks. Use when reviewing character bibles, outlines, scripts, or storyboards before human approval.
In this repositoryOne other file it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Stop with a blocked finding when a required approved source is missing or stale.
- Distinctive: line 17
Never rewrite source files, invent canon, or automatically approve an artifact.
- Very specific: line 19
Use scripts/validate_story.py first when the selected project follows the plugin's artifact contract.
≈ “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.
Files
Continuity Audit
Audit the user-selected story artifacts without modifying them.
Workflow
- Identify the current revision and every declared source reference.
- Stop with a blocked finding when a required approved source is missing or stale.
- Compare character identity, desires, permanent traits, temporary state, knowledge, props, time, and location across sources.
- Distinguish confirmed facts from inferred and unresolved statements.
- Report each problem with a severity, exact location, expected value, actual value, source evidence, and the smallest safe fix scope.
- Never rewrite source files, invent canon, or automatically approve an artifact.
Use scripts/validate_story.py first when the selected project follows the plugin's artifact contract. Structural validation does not replace creative continuity review.
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
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.