agentleFS
Sign inStart free
BenitoowBenitoow/cinema-skills/skills/color-script/SKILL.md

color-script

Skill0 starsChanged 41 days agoMITView on GitHub

Build a color script (palette and grade direction per story beat) from a synopsis, scene list or edit. Use when the user wants a color palette for a film, a look-development plan, grade notes for DaVinci Resolve or similar, or emotional color mapping.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. EVZheng-Lab/color-script★ 18same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Ask only for what is missing:

    line 16
  2. Distinctive:

    Look references (films, photos, moods) and any colors that must not be used

    line 19
  3. Distinctive:

    Keep continuity logic: a color that appears early should return, transformed, at the payoff.

    line 27
  4. Distinctive:

    Check readability: skin tones must stay believable, subtitles must stay legible against the palette.

    line 29
  5. Distinctive:

    Start with a one-line color concept (the idea in a sentence).

    line 33
  6. Distinctive:

    No invented story. Work from the beats given.

    line 51
  7. Distinctive:

    Do not promise exact colors: lighting, camera and display all change the result.

    line 53

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

Color Script

A color script maps emotion to color across the story. Produce one that a colorist or editor can apply directly.

Inputs to collect

Ask only for what is missing:

  1. The story or scene list (required), with the emotional arc if known
  2. Look references (films, photos, moods) and any colors that must not be used
  3. Delivery space: SDR (Rec.709) or HDR, and whether the footage is log or already graded
  4. Grading tool (DaVinci Resolve, Premiere Lumetri, After Effects, other)

Process

  1. Identify the beats (opening, disruption, escalation, climax, resolution) and the emotion of each.
  2. Assign each beat a dominant color family, an accent color, a contrast level (low / medium / high) and a saturation level.
  3. Keep continuity logic: a color that appears early should return, transformed, at the payoff. Name the motif.
  4. Translate each beat into grade direction: color temperature shift, tint, contrast curve behavior, shadow/highlight color bias, saturation strategy. Use descriptive terms and relative moves, not claims about a specific proprietary LUT.
  5. Check readability: skin tones must stay believable, subtitles must stay legible against the palette.

Output format

Start with a one-line color concept (the idea in a sentence).

Then a table, one row per beat:

BeatEmotionDominantAccentContrastSaturationHex swatches (3-5)Grade direction
  • Hex swatches are suggestions for reference boards and UI mocks, not guaranteed to match on-screen skin or footage.
  • Grade direction examples: "cool the shadows toward teal, keep highlights near neutral, lower mid-tone saturation, firm contrast"; "warm global temperature, lift blacks slightly, gentle roll-off".

Then:

  • Motif: the color that carries meaning across the film and how it evolves
  • Continuity warnings: where grades must match across cuts
  • Resolve starter nodes (only if the user uses DaVinci Resolve): suggested node order such as input conversion, primary balance, look, secondary skin protection, output. Keep it generic.

Rules

  • No invented story. Work from the beats given.
  • State when a choice is a taste decision versus a technical necessity.
  • Do not promise exact colors: lighting, camera and display all change the result. Recommend testing on a graded still before committing.

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