CC flash-reel
Generates a 30-second 9 16 cinematic reel from a user prompt (setting + vibe + rough storyline). Flash Reel — 30s Cinematic Reel Skill When to use User provides: a setting, a vibe/mood, and optionally a rough storyline. They want a ~30 second 9:16 reel with hard cuts every 3-4 seconds, anchored by one or more characters with reference photos, in a 35mm flash-photography aesthetic.
The skill promises to generate a 30-second 9:16 reel with hard cuts every 3–4 seconds, anchored by character references and a 35mm flash-photography aesthetic. One file, intact links, no critical errors. Code quality scores 71, execution process 53—the logic runs, but instructions may be incomplete or need field testing. No sandbox runs or examples show how it handles actual requests: whether it generates proper montage scripts or just frame descriptions.
Worth trying if you're prepared to iterate and refine prompts. For production work, test on simple scenarios first.
Generates a 30-second 9 16 cinematic reel from a user prompt (setting + vibe + rough storyline).
As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6203 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 6203 tokens
- 85Steps. 44 steps, 2 vague phrases
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 383: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 44 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.