agentleFS
Sign inStart free
badgidsbadgids/Story-Film-Skills/skills/continuity-check/SKILL.md

continuity-check

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Audit canon, story, screenplay, production documents, and generation prompts for identity, wardrobe, prop, geography, knowledge, time, lighting, audio, and dialogue continuity conflicts.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read core contract and CONTINUITY_RULES.md.

    line 13
  2. Very specific:

    Write 03_preproduction/continuity.md with sections: locked facts, approved reference versions, current scene states, conflicts, …

    line 15
  3. Very specific:

    Update canon when the user or an authoritative upstream edit settles a fact.

    line 18
  4. Distinctive:

    Run the project validator for deterministic ordering checks, then separately review motivation, performance, and dramatic logic that a …

    line 19

≈ “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

Continuity Check

Workflow

  1. Read core contract and CONTINUITY_RULES.md.
  2. Determine the requested scope and read every authoritative artifact, approved reference record, and the relevant entries from 01_story/story_state.json when present.
  3. Write 03_preproduction/continuity.md with sections: locked facts, approved reference versions, current scene states, conflicts, resolutions, unresolved questions.
  4. For each conflict, cite the two project artifacts by path and stable ID.
  5. Resolve by authority order. Never quietly pick the more convenient prompt.
  6. Update canon when the user or an authoritative upstream edit settles a fact. Use story-state when the change is chronological or mutable rather than permanent canon.
  7. Run the project validator for deterministic ordering checks, then separately review motivation, performance, and dramatic logic that a structural validator cannot prove.

Done

There are zero unresolved contradictions that would cause a character, prop, location, action, dialogue line, or audio cue to change identity across adjacent production artifacts.

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.

Check your setup, free