ericrisco/rsc-harness / skills/video-shorts
video-shorts
VerifiedUse when scripting or directing the edit of a single vertical short that has to hold attention from the first frame — turning a topic, a clip or a long video into a shot-by-shot script and an edit decision sheet, fixing a hook that dies in second three, generating hook variants to test, and planning cuts and on-screen text. NOT scheduling or cross-platform cadence (that is `social-publisher`), NOT running the editorial calendar (that is `content-engine`), NOT defining the durable brand tone (that is `brand-voice`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.2 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/cases.yaml | config | 3.4 KB |
| references/hook-and-script-patterns.md | markdown | 4.3 KB |
| references/specs-and-safe-zones.md | markdown | 3.5 KB |
| scripts/verify.shexecutable | script | 6.2 KB |
evals/README.md
View on GitHub# Evals — video-shorts
These cases are routing + capability checks for a human or an LLM judge; there is
no automated runner beyond `scripts/verify.sh` (which lints an emitted script file,
not these prompts). To run them: read `cases.yaml` and confirm the skill's
`description` would fire on every `should_trigger` prompt — including the
non-obvious "my Reels lose everyone in the first 3 seconds" symptom and the Spanish
"convierte este vídeo largo en un Short" phrasing — and that each `should_not_trigger`
prompt routes to the named sibling instead (`social-publisher`, `content-engine`,
`brand-voice`, `ads`, `podcast`) rather than here. For the `capability` scenario,
generate the script + EDS and grade it line by line against the `must_include`
rubric: a 0:00–0:03 hook with 4–7-word on-screen text, a timecoded beat sheet that
sums to a 15–30s runtime, on-screen text on every beat, a cut-cadence note, a loop
seam or single CTA (no outro), and the 9:16/1080×1920/burned-in-caption export note.
To lint an actual produced script, point `scripts/verify.sh` at the `.md` it emitted.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |