konradre/video-production-skills / skills/film-preprod
film-preprod
VerifiedPre-production of a SHORT FILM or a MUSIC VIDEO: the veto map from whoever judges it, the story written end-first (the seven steps in seconds, a subworld per beat), premises ranked twice, the hero shot generated first, the track map measured before the gen map, the shared pre-production core (partitions on continuity, the script diff) and contest hygiene. Use when a film or a music video is briefed, a premise or format must be chosen, a beat sheet must be written or checked, a track must be mapped, or contest rules must become a checklist. Triggers — "story beats", "the seven steps", "the premise", "which format, live action or animation", "the hero shot", "self-revelation", "track map", "cut to the drop", "the jury", "the veto map", "the contest rules". Not for an ad campaign's brief or cost plan — use ad-spot-preprod. Not for the reference set — use video-refs-continuity. Not for the prompt itself — use video-prompt-dialects. Not for the cut — use video-edit-edl.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.9 KB |
| references/CONTEST-HYGIENE.md | markdown | 2.2 KB |
| references/HERO-SHOT-AND-FORMAT.md | markdown | 3.4 KB |
| references/JURY-AND-PREMISE.md | markdown | 3.7 KB |
| references/MUSIC-VIDEO.md | markdown | 15.0 KB |
| references/STORY-METHOD.md | markdown | 5.2 KB |
| scripts/arc_check.pyexecutable | script | 4.3 KB |
| scripts/beat_calc.pyexecutable | script | 4.0 KB |
| scripts/premise_rank.pyexecutable | script | 3.1 KB |
| scripts/track_map.pyexecutable | script | 4.9 KB |
references/CONTEST-HYGIENE.md
View on GitHub# Contest hygiene — only when entering one
Read the rules snapshot AND the enforcement particulars ("find out the particulars of each"); the
ladder of consequences reaches WIP cuts, not just the final. What bit, in order:
- **Two clocks**: the race (a tie-break that rewards the earlier first-publication date, immutable)
and the final deadline. Lock the premise BEFORE publishing WIP — continuity binds a published
project to a good-faith continuation; a granted project cannot be unpublished.
- **Where generation must happen**: every AI video/image generation inside the one contest project on
the platform, within the window. External POST is permitted (cut, grade, mask, titles, non-AI 3D);
**external AI upscale, interpolation, relight and a NLE's neural tools are disqualifiers** — an
external upscaler is not available; the reconstruction is the platform's own, one pass on the locked cut.
- **The audio asymmetry**: audio may be generated OFF-platform, but **every sound must be AI-generated**,
ownership and licensing irrelevant — in the final AND in every published WIP cut; no temp track,
ever; every file uploaded to the project; a file → tool → version → date manifest.
- **Likeness**: no identifiable real person's likeness or voice, including your own and historical
figures, with no consent exception; characters who read as under 18 are prohibited.
- **Content**: no political or religious STATEMENT (a mythic structure is fine; a statement is not);
no third-party IP, brands or logos.
- **Retention**: generation history, prompts, project files and audio provenance archived for the
audit period (24 months); the final cut must reconcile against the project's own generation history.
- **Submission**: runtime floor, aspect, container, subtitles or VO, watermark and packshot on the film
and the post, a public post from a public account viewable logged out, the roster locked, metadata
and tags complete, before the deadline in the rules' time zone.
- **Ask what the rules do not say** (how many entries per person, whether a grey-zone tool counts as
generation) in-product before spending.
A production may pivot away from a contest; the method above survives as a checklist and carries no
project state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |