agentleFS
LordVayronLordVayron/video-factory/.claude/skills/story-architect/SKILL.md

story-architect

Skill67 starsChanged 18 days agoMITView on GitHub

The writers' room for every video in this factory. Turns a request into a premise, a script and a scene/blocking plan using real comedy and drama craft (game of the scene, heightening, misdirection, character-specific jokes, punch-up passes, a scored rubric), in English or Mexican Spanish. The script is the most important part of every video; nothing is drawn or filmed until the user approves it. Use when starting any video, episode, ad or skit, when a script feels flat, or when the user says "write the story", "write the episode", "give me ideas", "escribe el guion".

6 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. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read references/comedy.md before writing anything funny.

    line 10
  2. Distinctive:

    Premises (private): Write 10 one-line "what if" premises for the characters and format.

    line 13
  3. Very specific:

    No images exist yet. Revise until approved.

    line 28
  4. Distinctive:

    No line restates what we can see.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Story architect (the writers' room)

The script is the product. Pretty footage of a dull script is a dull video. The standard: every line earns its place, the dialogue has character and attitude, and the video works even muted.

Read references/comedy.md before writing anything funny. Read references/storytelling.md for non-comedy formats.

Process (fast: ~5 minutes of writing, one approval)

  1. Premises (private). Write 10 one-line "what if" premises for the characters and format. Each = base reality + one unusual thing. Kill anything generic ("X does a performance review"). Keep the 3 with the most specific, visual, character-driven game.
  2. Find the game. For the best premise, state it in one sentence: "The game is: ___." List 5 heightening moves ("if this is true, what else is true?"). Keep the 3 that escalate, and order them so the biggest is last.
  3. Draft fast. Full script with no pausing. Placeholders (****) are fine.
  4. Punch-up pass. For every punchline, write 3–5 alternatives and keep the funniest. Check word choice: the specific, funnier word (yardstick, not ruler). Put the funniest word last. Cut every line that only explains or sets up without a turn.
  5. Character pass. Each line must only be sayable by that character (for example: the schemer is precise, corporate, wounded pride; the sidekick is literal, joyful, wrong for the right reasons; the deflator is dry and sees through everyone). Swap the names: if a line still works, rewrite it.
  6. Visual pass. The first 1.5 s works as a freeze-frame, every beat has a visible action, and the ending reads with the sound off.
  7. Score it (references/comedy.md rubric). Under 8 average or any criterion under 7: rewrite before showing.
  8. Scene and blocking plan. Group shots into scenes (one location and moment each, ≤ 15 s, 2–5 shots of 2–5 s). Per scene, write the blocking sheet: where everyone sits or stands, which way they face, what they hold, and where they move (and when). This text goes into every storyboard and video prompt.

What the user sees (the only writing gate)

A single message with:

  • Logline and the game (one line each).
  • The script as a table read: SHOT · who · line, with stage directions in italics.
  • The 2 alternative punchlines for the main laugh and the button, so they can pick.
  • Runtime and estimated cost. No images exist yet. Revise until approved. Then hand the plan to cinematographer.

Hard rules

  • Hook in 0–1.5 s: an image that makes the viewer ask a question.
  • Beats join with "but" or "therefore", never "and then".
  • No line restates what we can see. No "As you know…". No jokes explained after they land.
  • Dialogue lines are ≤ 12 words and sound spoken. People interrupt, deflect and answer the wrong question.
  • The button tops the biggest laugh, or flips it. Never end on a line that merely summarizes.
  • Spanish: write natively in Mexican Spanish (no Spain-isms); never translate a joke literally.

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.