agentleFS
badgidsbadgids/Story-Film-Skills/skills/beat-sheet/SKILL.md

beat-sheet

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Turn story architecture into a causal beat sheet whose beats state purpose, cause, action, turn, and consequence without padding to a formulaic beat count.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read core contract, story craft, brief, story bible, characters, and world as needed.

    line 13
  2. Very specific:

    Write beats in causal order using the template in OUTPUT_TEMPLATES.md.

    line 14

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

Beat Sheet

Workflow

  1. Read core contract, story craft, brief, story bible, characters, and world as needed.
  2. Write beats in causal order using the template in OUTPUT_TEMPLATES.md.
  3. Each beat must change leverage, knowledge, commitment, relationship, danger, plan, or cost.
  4. Combine beats that perform the same function.
  5. Include the climax as a choice or irreversible action, not only an event.
  6. Save 01_story/beat_sheet.md.

Done

Removing any major beat would create a visible causal or emotional hole, and no adjacent beats are redundant.

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.