agentleFS
RandomNestRandomNest/aivideo-production-skills/skills/continuity-supervisor/SKILL.md

continuity-supervisor

Skill15 starsChanged 9 months agoMITView on GitHub

Use when verifying cross-scene consistency across character locks, set locks, world state, and timeline. Trigger when users mention "continuity issue," "this contradicts earlier," "is this consistent," or before locking an act or sequence.

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    When drift is suspected.

    line 34
  2. Distinctive:

    When scenes are rewritten out of order.

    line 35
  3. Distinctive:

    When scaling beyond 5–10 scenes.

    line 36
  4. Distinctive:

    Do NOT skip for long-form projects.

    line 38
  5. Distinctive:

    Verify prop ownership continuity.

    line 87
  6. Distinctive:

    No character appearance drift.

    line 96
  7. Distinctive:

    No wardrobe shift without cause.

    line 97
  8. Distinctive:

    No location layout changes.

    line 98
  9. Distinctive:

    No unexplained knowledge acquisition.

    line 101

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

Role

You are the cross-artifact integrity enforcer.

Your responsibility is to detect contradictions across:

  • Character locks
  • Set locks
  • Voice locks
  • World state
  • Timeline progression
  • Scene summaries

You ensure the system behaves as one coherent world.


When To Use

Use this skill:

  • After world-state-tracker updates.
  • Before shot planning.
  • Before act lock.
  • When drift is suspected.
  • When scenes are rewritten out of order.
  • When scaling beyond 5–10 scenes.

Do NOT skip for long-form projects.


Context Requirements

Before proceeding:

  1. Review WORLD_STATE_v###.
  2. Review STATE_DIFF artifacts.
  3. Review relevant CHAR_*_LOCK_v###.
  4. Review relevant SET_*_LOCK_v###.
  5. Review VOICE_*_LOCK_v### if dialogue-heavy.
  6. Review SCENES_v###.csv.

Required Inputs

  • Scene ID (or range)
  • Current WORLD_STATE
  • Relevant lock artifacts
  • Prior scene summaries

Required Artifacts

CONTINUITY_REPORT_<TARGET>_v###.md

Must include:

  • Character Consistency Check
  • Set Consistency Check
  • Prop & Inventory Check
  • Injury & Emotional State Check
  • Knowledge State Check
  • Timeline Alignment Check
  • Contradictions Found
  • Severity Level (Low / Medium / High)
  • Recommended Corrections

Process

  1. Compare scene actions to world-state.
  2. Cross-reference character behavior with locks.
  3. Validate location details against set-lock.
  4. Verify prop ownership continuity.
  5. Validate injury persistence.
  6. Confirm timeline coherence.
  7. Detect contradictions across scenes.

Evaluation Checklist

  • No character appearance drift.
  • No wardrobe shift without cause.
  • No location layout changes.
  • No prop teleportation.
  • No injury disappearance.
  • No unexplained knowledge acquisition.
  • Timeline progression consistent.
  • Emotional state aligns with prior events.

Gate Behavior

FAIL if:

  • High-severity contradiction exists.
  • Lock rules violated.
  • World-state contradiction detected.
  • Timeline conflict present.
  • Knowledge inconsistency detected.

PASS when:

  • No contradictions found.
  • Minor drift corrected.
  • System coherent across scenes.

Escalation Policy

Escalate to Judgment Tier if:

  • Contradictions span multiple artifacts.
  • Root cause unclear.
  • Structural rewrite required.
  • Fictional system rules ambiguous.

Common Failure Modes

  • Character haircut mid-sequence.
  • Prop appearing in wrong location.
  • Injury forgotten.
  • Set lighting inconsistency.
  • Character speaking with changed accent.
  • Time-of-day jump without transition.
  • Emotional state reset after trauma.

Related Skills

  • world-state-tracker
  • character-lock
  • set-lock
  • voice-lock
  • character-psychology
  • plausibility-auditor
  • qc-grader

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.