agentleFS
PicsArtPicsArt/gen-ai-skills/skills/film-story-writing/SKILL.md

film-story-writing

Skill7 starsChanged 21 days agoMITView on GitHub

Write a short film's story and break it down - pre-setting the look from the idea, the ten-line story and every scene as what the viewer sees and hears, dialogue that performs action, one light per scene with its dark side and a colour kept back, and the shot cards and asset tags that come out of it. Use when a film needs its look suggested, its story written or rewritten, or its story turned into shots and assets.

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:

    every scene has action, and every object belongs to the world and its period.

    line 60
  2. Very specific:

    Every shot becomes a card, as references/breakdown.md says: the action and the line copied from the story, who and what is in frame by tag, …

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Film story

The story is written for the viewer, in the viewer's words. The shot list is written from the story and never the other way round. Read these before the step they serve:

FileRead it before you…
references/story.mdwrite or rewrite the story, or its viewer track
references/dialogue.mdwrite a spoken line
references/breakdown.mdturn the story into shot cards and asset tags
references/look.mdsuggest a look, or use the user's reference images
references/light.mdset a scene's light on its cards, or keep a colour back for one moment
references/writers-room.mdthe user asks for a writers' room, or for several drafts to choose from

Suggest the look from the idea

The look comes before the story, because genre decides how the story is told. Pre-set picsart_film_setup from the idea with suggested, one line of why per value:

  • The genre the events make. Two people fighting is action; two people talking is drama. A custom genre is the user's own words.
  • A tone only when the story names a period or a tradition of cinema. A tone is an era recipe: it sets the rig, not the colour. Otherwise leave it on auto. The console expands a tone into its camera and lens pills before applying any pill you also name, so an explicit camera or lens wins over the tone's.
  • Only the console's own controls. The lens is a glass family, never a focal length. Focal length, aperture, framing, shot length and camera movement are per-shot choices on picsart_film_shotlist; grain rides in the camera preset; pace is written per shot, never set. Ids the console does not have are ignored, not guessed at.
  • The colour only when the idea names one: one line of direction as paletteHint, written as a scheme around a hue ("analogous around amber"). The console shows it as a hint and applies nothing; it has no palette to pre-set. The colour is the user's; suggest, never decide it.
  • The frame from the user's own words (vertical, 9:16 and tiktok resolve the same), and the runtime they said. The console offers only the five frames video models render broadly (16:9, 4:3, 1:1, 3:4, 9:16): for scope or 21:9, shoot 16:9 and crop in the edit.
  • Where each goes. film (the title) is required, and paletteHint is its own top-level argument. Genre, tone, ratio and duration all go inside suggested.selections, in those field names, never as top-level arguments: the schema allows nothing else. The why lines go in suggested.why, keyed the same way.

Pass only what the material answers and leave the rest on the console's defaults: a wrong prefill reads to the user as a decision someone already made. The console's presets are its own; choose ids from it and never write a preset's text yourself.

Write the story

Ten lines at the top, then every scene in order, as references/story.md says. Before you show it, check:

  • the thing the story is about is seen in the first scene;
  • who holds what, and where people are, is visible, not implied;
  • the events belong to the genre;
  • nothing contradicts what the user's brief fixed;
  • every scene has action, and every object belongs to the world and its period.

These are your checks as the writer, never a stranger's read. Then write the film's viewer track (references/story.md): what a viewer who knows nothing must get, and by when. Whether a stranger gets it is decided by quality-review's cold watch on the animatic and the cut, never by you or a critic who has read the story.

State the identity budget you inferred ("two faces and one garage"); never ask the user to choose it. A short affords two or three faces and one to three rooms comfortably. A crowd is one asset with a count.

A note about what happens is answered with the rewritten paragraph, shown whole. Never with a shot list, a table or options. A fixed fact the note would touch is the user's to change, not yours.

Break it down

Every shot becomes a card, as references/breakdown.md says: the action and the line copied from the story, who and what is in frame by tag, what each visible face feels (held in, except the peak shot's face: "@teo relief, unguarded: the tears come", the word unguarded and what shows, on that one card only), the seconds and the camera. Every person, place and prop the film shows gets a tag, and every lasting change the story makes to one gets a tag of its own.

Write the story, not the videos. The story is never stretched to fill a model's ceiling or cut to fit it, and a scene never changes place to make a video edge. The edges are made by the camera, later.

Traps

  • Writing a drama under an action look, or keeping a story after the genre changed. Rewrite the story first.
  • A story in film words ("we open on a wide"). A reader who knows nothing about film reads it as the film.
  • Softening a fight or a fire to protect the render. Action, crowds, water and fire are not cost flags.
  • Vague choices: "moody", "cinematic", "looks emotional". Write what is seen.
  • A shot longer than its action, to fill a run.
  • Leaving out what each face feels. Every card carries it.
  • Treating the user's photo of a real person as a mood reference. It is the person.

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.