SkillAgentSearch skills...

storyboard-shot-breakdown

Break down each shot and turn the analysis into a storyboard reference

Install / Use

npx skills add 0xsline/OpenChatCut --skill storyboard-shot-breakdown

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of storyboard-shot-breakdown

storyboard-shot-breakdown scores 83/100 on our quality scale, 3106th of 4,700 Development & Engineering skills we index.

Its SKILL.md is 3.5 KB long, split into 6 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,986 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
16/20
Description
12/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so storyboard-shot-breakdown is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

storyboard-shot-breakdown compared with similar skills

All 4 of these similar skills score higher than storyboard-shot-breakdown; compare them before choosing.

SkillScoreStarsUpdatedFormat
storyboard-shot-breakdown (this skill)by 0xsline832.0k56d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install storyboard-shot-breakdown?
Run npx skills add 0xsline/OpenChatCut --skill storyboard-shot-breakdown. The install tabs above show the steps for each supported agent.
Which AI agents does storyboard-shot-breakdown work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is storyboard-shot-breakdown safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is storyboard-shot-breakdown still maintained?
The repository was last updated about 2 months ago, so storyboard-shot-breakdown is actively maintained.

name: storyboard-shot-breakdown description: Break down each shot and turn the analysis into a storyboard reference. Use when the user wants shot-by-shot film analysis, director logic, cinematography breakdown, or a storyboard-style reference from a video.

Storyboard Shot Breakdown

Use this skill to analyze a video shot by shot and produce a storyboard-style reference that explains the director's visual decisions.

Core Philosophy

Do not merely describe what is visible. Deduce why each visual choice was made.

Analyze each shot across five director-decision dimensions:

| Dimension | Core question | | ------------------ | ------------------------------------------------------------------------------------------------------------ | | Composition | What is the viewer forced to look at? What pressure does space, symmetry, depth, or framing create? | | Focal length | What psychological distance does the lens create? Does it compress, expand, isolate, or invade? | | Movement | Why does the camera move or stay still at this exact moment? What changes before and after? | | Cut | Why cut here instead of earlier or later? Is the driver emotion, story, rhythm, eye trace, action, or sound? | | Narrative function | What new information does this shot deliver: setup, turning point, emphasis, concealment, revelation? |

Workflow

  1. Read project state and source media.
  2. Read transcript or audio context when available so narrative interpretation is grounded.
  3. Detect or mark shot boundaries with available OpenChatCut/media tooling.
  4. Extract representative frames for each shot in batch when possible.
  5. Inspect frames before writing analysis. Do not invent details that are not visible.
  6. For high shot counts, tell the user the count and offer output scope choices before spending effort.
  7. Analyze each selected shot using the five dimensions.
  8. Summarize the overall visual rule of the scene in 1-2 concise sentences.
  9. Generate a storyboard reference image or structured analysis artifact if the user wants a visual output.

Internal Reasoning

Use a counterfactual test: if the conventional alternative were used, what emotion or information would be lost? The answer is usually the director's motive.

Use this reasoning to improve the analysis, but do not output the counterfactual test as a separate section unless the user asks.

Output Format

Per shot:

S{N} - {scale} · {lens/mood} · {movement} · {timecode} · {duration} · {narrative function}

Composition: [what attention is forced onto and what pressure the frame creates]
Focal Length: [psychological distance and dramatic effect]
Movement: [why it moves or stays still, and what changes]
Cut: [why the cut lands here, including rhythm/eye trace/sound when relevant]
Narrative: [what story information this shot adds]

Overall:

Director's Logic: [3-5 sentences summarizing the visual strategy]
Visual Rule: [1-2 sentences the user can reuse as a shooting/editing reference]

Rules

  • Write from visible evidence and available transcript/audio context.
  • Do not borrow details from adjacent shots unless clearly stated as sequence-level analysis.
  • Keep shot numbering stable.
  • User owns scope trade-offs: if output must be reduced, propose choices.
  • Prefer current OpenChatCut/media tools over hardcoded local commands. Use external scripts only when they are available and clearly help.

Related Skills

View on GitHub
GitHub Stars2.0k
CategoryDevelopment
Updated1mo ago
Forks294

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions