agentleFS
Sign inStart free
RandomNestRandomNest/aivideo-production-skills/skills/world-state-tracker/SKILL.md

world-state-tracker

Skill15 starsChanged 9 months agoMITView on GitHub

Use when updating and maintaining the canonical state of the story world across scenes. Trigger when scenes introduce injuries, knowledge changes, prop ownership shifts, time progression, or environmental changes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    After every scene is validated.

    line 32
  2. Distinctive:

    After any state-changing event.

    line 33
  3. Distinctive:

    Before drafting the next scene.

    line 34
  4. Distinctive:

    Before shot planning (to ensure visual consistency).

    line 36
  5. Distinctive:

    Do NOT skip this step in long-form production.

    line 38

≈ “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 canonical memory system of the narrative.

Your responsibility is to maintain an explicit, versioned representation of:

  • Character state
  • Knowledge state
  • Injuries
  • Prop ownership
  • Timeline progression
  • Environmental changes
  • Rule changes (if fictional system)

You prevent hidden memory reliance.

When To Use

Use this skill:

  • After every scene is validated.
  • After any state-changing event.
  • Before drafting the next scene.
  • When contradictions appear.
  • Before shot planning (to ensure visual consistency).

Do NOT skip this step in long-form production.

Context Requirements

Before proceeding:

  1. Review WORLD_STATE_v###.json.
  2. Review PLAUS_<SCENE_ID>_v###.md.
  3. Review BREAKDOWN_v###.csv.
  4. Review character-psychology output (if relevant).

Required Inputs

  • Prior WORLD_STATE_v###.json
  • Scene ID
  • Scene outcome
  • State changes identified in breakdown

Required Artifacts

1. STATE_DIFF_<SCENE_ID>_v###.json

Must explicitly list:

  • Property changes
  • Knowledge acquisition
  • Injury updates
  • Location state changes
  • Time progression

2. WORLD_STATE_v###.json

Updated canonical state after applying diff.

Structure Requirements

WORLD_STATE must include:

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