opencode-skills-collection 4.0.73 → 4.0.74

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-09-25T02:13:20.897Z",
+  "updatedAt": "2026-09-26T02:19:01.177Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -941,6 +941,7 @@
     "file-path-traversal",
     "file-uploads",
     "filesystem-context",
+    "film-crew",
     "find-bugs",
     "find-complementary-founders",
     "find-matching-tenders",
@@ -2206,6 +2207,7 @@
     "test-fixing",
     "test-framework-migration-skill",
     "test-guard",
+    "testdriver-e2e-testing",
     "testing-patterns",
     "testing-qa",
     "testng-skill",

package/bundled-skills/film-crew/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: film-crew
+description: "Turn a one-line AI video idea into a shot list and per-shot, model-ready prompts via a film crew (director, DP, gaffer, editor, script supervisor). Also fixes failing video prompts and diagnoses bad clips before a reroll. Works with Wan, LTX, Kling, Veo, Seedance, Hailuo, Runway."
+category: media
+risk: safe
+source: "https://github.com/HEOJUNFO/ai-film-crew/tree/533f61be2741c10932c6c86e47777cac9ffe3fe4/skills/film-crew"
+source_repo: HEOJUNFO/ai-film-crew
+source_type: official
+date_added: "2026-09-25"
+author: HEOJUNFO
+license: MIT
+license_source: "https://github.com/HEOJUNFO/ai-film-crew/blob/533f61be2741c10932c6c86e47777cac9ffe3fe4/LICENSE"
+tags: [video, text-to-video, shot-list, prompting, film]
+tools: [claude, codex, cursor, gemini]
+---
+
+# Film Crew
+
+You are the producer. You don't write one prompt and hope. You run the idea past a crew,
+each with one job, then hand the user a shot list and one prompt per shot that a video
+model can actually execute.
+
+Most failed AI video clips fail for boring, fixable reasons: two actions in one clip,
+no camera instruction, a subject described differently in every shot, physics the model
+can't do in 5 seconds, or a prompt that describes a *feeling* instead of a *frame*.
+The crew exists to catch those before generation, and to diagnose them after.
+
+## When to Use This Skill
+
+- Use when someone wants to plan an AI video (ad, short, music video intro) before generating clips.
+- Use when a text-to-video or image-to-video prompt keeps failing and needs a diagnosis and rewrite.
+- Use after a bad generation to decide the one change to make before the next reroll.
+- Do not use it to generate, edit or render video; it produces planning documents and prompts only.
+
+## Modes
+
+Pick the mode from the request. Default is **Plan**.
+
+| Mode | When | Output |
+|---|---|---|
+| **Plan** | "make a video of…", an idea, a script, a product | `SHOT_LIST.md` + per-shot prompts |
+| **Fix** | user pastes a prompt that isn't working | diagnosis + rewritten prompt |
+| **Review** | user describes or shares a generated clip | what went wrong + the one change to make before the next reroll |
+
+## Plan mode
+
+### 0. Intake (keep it short)
+
+Only ask what you can't reasonably default. Ask at most 3 questions, in one message.
+If the user said "just go", use the defaults.
+
+| Field | Default |
+|---|---|
+| Platform / aspect | 9:16 vertical, short-form feed |
+| Total length | 15 s |
+| Target model | model-agnostic (write the generic adapter) |
+| Mode per shot | text-to-video, unless the user has a reference image. **Real product or real person → ask for a photo and use image-to-video**; text-to-video invents a different mug. |
+| Audio | none in the prompt, unless the target model generates audio *and* the user wants it in-model (otherwise add it in the edit) |
+
+### 1. Run the crew, in order
+
+Read each role file before running that role. Each role writes its own short section.
+Keep every section terse: the output is a production document, not an essay.
+
+1. **Director** → `references/roles/director.md` — logline, intent, beat sheet with timings, the hook.
+2. **Production designer** → `references/roles/production-designer.md` — the *continuity bible*: locked descriptors for every recurring character, prop and location.
+3. **Director of photography** → `references/roles/dp.md` — per shot: size, lens, angle, height, ONE camera move.
+4. **Gaffer** → `references/roles/gaffer.md` — time of day, key direction, color temperature, practicals, contrast.
+5. **Editor** → `references/roles/editor.md` — shot durations that fit the model's clip length, cut types, first-frame hook, ending.
+6. **Sound** → `references/roles/sound.md` — only if the target model generates audio, or the user will add music/SFX in the edit.
+7. **Script supervisor** → `references/roles/script-supervisor.md` — continuity + feasibility + "unslop" pass. Has veto power: any shot it flags gets rewritten before output.
+
+### 2. Write the prompts
+
+Read `references/model-prompting.md`. For each shot, assemble the prompt from the crew's
+decisions in this order, then run it through the target model's adapter:
+
+```
+[shot size + lens + camera move] of [subject, verbatim from the continuity bible]
+[doing ONE visible action, present tense], in [location, verbatim from the bible].
+[lighting from the gaffer]. [style / film look]. [audio line, only if supported]
+```
+
+This order is the generic default. When the target model's adapter specifies a different
+order, **the adapter wins**.
+
+Rules that apply to every model:
+- One subject action and one camera move per shot. Two actions = two shots.
+- Paste continuity descriptors **verbatim** in every shot: the FULL version when the whole subject is in frame, the TIGHT version for close-ups. Never paraphrase either.
+- Describe what the camera sees, not what the viewer should feel. "Tense" is not a frame; "sweat on the upper lip, jaw clenched, eyes on the door" is.
+- No on-screen text, logos or readable signage unless the model is known to render text. Add text in the edit.
+- Keep each shot within the model's max clip length (see adapter). Plan for 1–2 s of handles.
+- Image-to-video: describe only motion and camera. Don't re-describe what's already in the image.
+
+### 3. Output
+
+Write `SHOT_LIST.md` using `references/templates/shot-list.md`. If the user is working in a repo
+or folder, save it there; otherwise print it. Include:
+- the crew sections (short),
+- the shot table,
+- one copy-paste prompt block per shot (plus negative prompt where the model supports it),
+- a **reroll plan**: for each shot, the most likely failure and what to change if it happens.
+
+End with one line telling the user which shot is highest-risk and why.
+
+## Fix mode
+
+1. Read `references/roles/script-supervisor.md` and `references/unslop.md`.
+2. Name the specific problems in the pasted prompt (max 5, most damaging first).
+3. Rewrite it using the Plan-mode prompt order. If it contains two actions, split it into two shots and say so.
+4. Show before → after. Keep the user's intent; change the mechanics.
+
+## Review mode
+
+Read `references/reroll-review.md`. Diagnose from what the user describes or shares
+(frames, a clip, a description). Classify the failure, then give **one** change to make
+before the next generation. Changing five things at once means you learn nothing from the reroll.
+
+## Limitations
+
+- It plans, diagnoses, and rewrites prompts; it does not generate, edit, or render video.
+- Output quality depends on the target model's current clip limits and prompt handling, which change often. Check the model's own docs before trusting an adapter's defaults.
+- Continuity locks hold only as far as the model honors them; long sequences may still drift and need a reroll.
+- It has no way to see a clip unless the user shares frames, a file, or a description of what happened.
+
+## Tone
+
+Talk like a working crew: specific, fast, no hype. Use real film vocabulary (it helps the
+models), but explain any term the user might not know in 3–5 words the first time.

package/bundled-skills/film-crew/references/model-prompting.md

@@ -0,0 +1,89 @@
+# Model prompting adapters
+
+The crew's decisions are model-agnostic. This file turns them into the phrasing each model
+family tends to follow best.
+
+> Video models change every few months. Treat these as conservative defaults, check the
+> model's current docs for hard limits (clip length, resolution, prompt length), and send a
+> PR when something here goes stale.
+
+## Generic adapter (use when the model is unknown)
+
+One paragraph, present tense, concrete, in this order:
+
+1. Shot size, lens, camera move
+2. Subject (verbatim from the continuity bible)
+3. The one action
+4. Location (verbatim)
+5. Lighting
+6. Look / film stock
+7. Audio (only if the model generates audio)
+
+~40–90 words. Longer is fine for open-weights models; shorter for models with prompt
+rewriting ("prompt enhancement") turned on.
+
+## Open-weights models (Wan, HunyuanVideo, LTX-Video, Mochi, CogVideoX…)
+
+- **Be literal and long.** These models generally reward detailed, chronological,
+  paragraph-style descriptions (roughly 60–150 words): what's in frame, what moves, in
+  what order.
+- **Describe motion in sequence:** "…lifts the cup, pauses, then sets it down."
+- **Use the negative prompt** if your workflow exposes one:
+  `blurry, warped hands, extra fingers, morphing, flicker, text, watermark, logo, static frame, oversaturated`
+- **Seed discipline:** when rerolling to test a single change, keep the seed fixed so you
+  isolate the effect of the change.
+- Clip length is bounded by frame count and VRAM. Plan short shots and cut them together.
+
+## Kling
+
+- Structure: subject → movement → scene → camera → lighting → atmosphere.
+- Keep it tighter than open-weights prompts; one clear action.
+- Clip length is chosen from presets (commonly 5 s or 10 s). Plan with the editor's
+  fixed-length rule.
+- Negative prompt: use it where your version/interface exposes the field.
+- Some newer versions can generate audio. If yours does and the user wants in-model
+  sound, apply the audio rules from the Veo section; otherwise keep sound out of the prompt.
+- Image-to-video: describe only the motion and the camera; the image already carries the
+  look.
+
+## Veo (and other models that generate audio)
+
+- Write sound explicitly, as its own sentence(s):
+  - Dialogue: `The barista says, "Sorry — my fault."`
+  - SFX: `SFX: paper cup hits tile, liquid splash.`
+  - Ambience: `Ambient café murmur, espresso machine hiss.`
+- Keep dialogue short (one line per shot). Long lines drift out of sync.
+- Camera and lens terminology is followed well; use it.
+
+## Seedance and other multi-shot-capable models
+
+- If your version supports multiple shots in one generation, you can write the sequence
+  explicitly: `Shot 1: … Cut to Shot 2: …`. Keep each shot to one action and restate the
+  character descriptors in each.
+- If you need tight control, still generate shot by shot and cut in the edit.
+
+## Hailuo / MiniMax
+
+- Camera moves can be stated plainly in the prompt ("slow push-in", "pan left"). Some
+  versions and front-ends accept bracketed camera commands such as `[Push in]` or
+  `[Pan left]`; use them if your interface documents them.
+- Keep one move per shot even when the syntax allows chaining several.
+
+## Runway / Luma / Pika / Sora-style prompt-enhanced models
+
+- These often rewrite your prompt. Put the non-negotiables first (subject descriptors,
+  the action, the camera move) and keep the prompt short enough that the rewrite doesn't
+  bury them.
+- For image-to-video: motion + camera only.
+
+## Image-to-video (every model)
+
+The most reliable way to keep a character consistent across shots:
+1. Generate or pick **one** reference still per character/location.
+2. Use it as the first frame for every shot where they appear.
+3. In the prompt, describe **only** what moves and how the camera moves.
+
+## Clip length cheat sheet
+
+Check your model's current limit. Common ranges in practice: 4–10 s per generation.
+The editor role should never plan a shot longer than the limit minus ~1 s of handles.

package/bundled-skills/film-crew/references/reroll-review.md

@@ -0,0 +1,46 @@
+# Reroll review: change one thing, then reroll
+
+AI video is probabilistic. Some rerolls are just the dice. Many are the prompt. The job
+here is to tell those apart and change **one** thing at a time, so each reroll teaches you
+something.
+
+## 1. Classify the failure
+
+| Class | Looks like | Most likely fix |
+|---|---|---|
+| **Dice** | The prompt is followed, the clip is just weaker than the last one | Reroll unchanged (new seed). Nothing to fix. |
+| **Ignored action** | The key event doesn't happen (the cup never spills) | Make the action the *first* clause; describe its start and end; cut everything else in the shot |
+| **Two things fighting** | Half an action, half another | Split into two shots |
+| **Physics break** | Liquid behaves like jelly, objects pass through each other | Frame tighter, slow the action, simplify the background, lock the camera |
+| **Identity drift** | Character looks different from other shots | Paste the continuity descriptors verbatim, or switch to image-to-video from one reference |
+| **Camera chaos** | Warped geometry, swimming background | One move only, slower, or locked-off |
+| **Look drift** | Color/light changes between shots | Paste the gaffer's line verbatim; name the source and color temperature |
+| **Artifacting** | Extra fingers, melting faces, flicker | Tighter framing, fewer subjects, add the negative prompt if supported |
+| **Text garbage** | Nonsense letters | Remove readable text from the shot |
+
+## 2. Decide
+
+- Same failure twice in a row → it's the prompt, not the dice. Apply the fix.
+- Different failures each time → the shot is too ambitious. Simplify it (split, tighten, slow down).
+- 3+ rerolls with no improvement → go back to the DP and director: re-block the shot.
+
+## 3. Report format
+
+```
+CLASS: Ignored action
+EVIDENCE: in 4/4 clips the cup lands upright; no liquid leaves it
+CHANGE (one): lead with the action — "Black coffee sloshes out of a tipping paper cup…" —
+              and cut the barista from the frame
+KEEP: lens, light, seed policy
+```
+
+## A worked example
+
+The upstream [ai-film-crew repository](https://github.com/HEOJUNFO/ai-film-crew) shows ten generations of one prompt in its `assets/ten-rerolls.png`:
+*"A barista bumps a customer's elbow and a paper coffee cup slips and spills onto the café
+floor next to white sneakers, slow motion, handheld close-up, warm morning light."*
+
+Across ten rerolls the cup falls, rolls, or lands upright. The spill (the whole point)
+barely happens. Diagnosis: **two things fighting** (the bump and the spill share one shot)
+plus **ignored action** (the spill is the last clause). The crew fix is in the upstream repository's
+`examples/coffee-spill-15s/SHOT_LIST.md`.

package/bundled-skills/film-crew/references/roles/director.md

@@ -0,0 +1,38 @@
+# Director
+
+**Job:** decide what this video is *for* and what happens, beat by beat. Everyone else
+executes your call.
+
+## Output (keep it under ~12 lines)
+
+```
+LOGLINE: one sentence, subject + action + turn.
+INTENT: what the viewer should do/feel/understand at the end (one line).
+HOOK (0–1.5 s): the first frame. Must be legible with sound off.
+BEATS:
+  1. 0.0–2.5 s  — …
+  2. 2.5–6.0 s  — …
+  …
+ENDING: button / reveal / loop point.
+```
+
+## Rules
+
+- **Open on motion or a question, never on an establishing shot.** In a vertical feed the
+  first 1.5 s decides whether anyone sees the rest.
+- **One idea per video.** If you need "and also", it's two videos.
+- **Beats are visible events,** not moods. "She realizes" is not a beat; "she stops
+  mid-sip and looks at the receipt" is.
+- **Budget for the model.** A beat that needs complex physics (pouring, cloth tearing,
+  hands manipulating small objects, crowds interacting) gets its own short shot, framed
+  tight, with nothing else going on.
+- **Loop if you can.** For short-form, an ending that cuts cleanly back to frame one
+  earns rewatches.
+- Product videos: the product must be on screen, unobstructed, by beat 2. Hero it once,
+  in the gaffer's best light, with no hands in the hero shot. If hands are the point
+  (handmade, cooking, a demo), give them their own shots and keep the hero shot clean.
+
+## Questions to ask yourself before handing off
+
+- Could a stranger describe this video in one sentence after watching it once?
+- Which beat would I cut if I had to lose 3 seconds? (Cut it now.)

package/bundled-skills/film-crew/references/roles/dp.md

@@ -0,0 +1,28 @@
+# Director of photography (DP)
+
+**Job:** decide exactly what the camera sees in each shot and how it moves.
+
+## Output: one line per shot
+
+```
+S1  ECU | 100mm macro | eye level | locked-off        | 2.5 s
+S2  MS  | 35mm        | low angle | slow push-in      | 4 s
+S3  WS  | 24mm        | high angle| handheld, drifting| 3 s
+```
+
+Shot sizes: ECU (extreme close-up), CU, MCU (chest up), MS (waist up), MWS, WS (full body), EWS (establishing).
+
+## Rules
+
+- **One camera move per shot.** Push-in, pull-out, pan, tilt, truck (sideways), pedestal
+  (up/down), orbit, handheld, or locked-off. Combining moves ("orbit while pushing in and
+  tilting up") is the #1 source of warped geometry.
+- **Name the lens.** 24mm reads wide and energetic, 35–50mm natural, 85–135mm compressed
+  and intimate, macro for texture. Models respond to focal lengths.
+- **Match move speed to duration.** A 3-second shot gets a *slow* move or none.
+- **Tight on hard physics.** Pours, spills, hands and small objects: frame close, keep the
+  background simple, lock the camera or move it very slowly.
+- **Vertical framing (9:16):** stack the composition vertically; keep faces in the upper
+  third and important action out of the bottom 15% (UI overlays live there).
+- **Vary sizes between consecutive shots** (e.g. WS → CU), or the cut will look like a jump.
+- Avoid "cinematic" as a camera instruction. It's a vibe, not a shot.

package/bundled-skills/film-crew/references/roles/editor.md

@@ -0,0 +1,34 @@
+# Editor
+
+**Job:** make the shots add up to a video: durations, order, cuts, pacing. You think about
+the timeline, not the frame.
+
+## Output
+
+```
+TOTAL: 15.0 s  (sum of shots, trimmed)
+S1 2.5 s  → hard cut
+S2 4.0 s  → match cut on motion
+S3 3.0 s  → smash cut
+…
+GENERATE: each shot +1 s handles (so S2 is generated at 5 s, used at 4 s)
+HOOK CHECK: frame 1 is S1 ECU, motion starts at 0.2 s ✅
+LOOP: last frame of S5 matches S1 composition ✅/❌
+```
+
+## Rules
+
+- **Fit the model.** Every shot must be ≤ the model's max clip length (see
+  `references/model-prompting.md`). If a beat needs longer, split it into two shots with a
+  change of angle.
+- **Generate long, use short.** Plan 0.5–1 s of handles at each end. The first and last
+  frames of AI clips are often the weakest.
+- **Fixed-length models** (only preset lengths such as 5 s / 10 s): generate at the
+  shortest preset and pick the strongest section. A 2.5 s shot uses the best 2.5 s of a
+  5 s clip; note which section in the timeline.
+- **Short-form pacing:** 1.5–3 s per shot is normal; a 6 s static shot kills retention
+  unless something is happening in it.
+- **Cut on action.** If S1 ends with a hand moving right, S2 should start with motion
+  continuing right.
+- **Text goes in the edit,** not the prompt. Note captions/supers here with timings.
+- Call out any shot that exists only for coverage. Coverage costs generations.

package/bundled-skills/film-crew/references/roles/gaffer.md

@@ -0,0 +1,30 @@
+# Gaffer
+
+**Job:** light the scene so it looks intentional and stays consistent between shots.
+
+## Output
+
+```
+TIME / SOURCE: late afternoon sun through west window (motivated)
+KEY: camera-left, 45°, soft
+FILL: low, bounce from white tabletop
+RIM / BACK: warm sun edge on hair
+COLOR TEMP: warm key ~3200K vs cool ambient ~5600K
+CONTRAST: medium-high, deep shadows
+PRACTICALS: pendant bulbs visible in background, slightly blown
+LOOK: 35mm film, fine grain, mild halation
+```
+
+## Rules
+
+- **Motivate the light.** Say where it comes from (window, neon sign, streetlight,
+  monitor glow). Unmotivated "dramatic lighting" gives you random results.
+- **Same key direction in every shot of a scene,** or the cut breaks continuity.
+- **Contrast beats brightness.** Flat, evenly lit prompts are what make AI video look
+  like AI video. Ask for shadows.
+- Color: pick one warm/cool contrast and hold it. Write it in plain words plus a
+  temperature if useful.
+- Night scenes: name the sources (sodium streetlight, phone screen, neon). "Dark" alone
+  gets you murk.
+- Products: soft key, clean rim to separate from background, a highlight that shows the
+  material (gloss, brushed metal, glass).

package/bundled-skills/film-crew/references/roles/production-designer.md

@@ -0,0 +1,43 @@
+# Production designer
+
+**Job:** make the world consistent. You write the **continuity bible**: the exact words
+every other role must paste, verbatim, whenever a character, prop or location appears.
+
+Video models have no memory between clips. The *only* continuity you get is identical
+wording. Paraphrasing a character ("a woman in a red coat" → "the lady in crimson")
+gives you a different person.
+
+## Output
+
+```
+CHARACTERS
+  C1  <age range> <build> <hair: length, color, style> <skin tone> <face detail>,
+      wearing <top, color, material> and <bottom>, <one distinctive accessory>
+LOCATIONS
+  L1  <place type>, <era/style>, <3 concrete set details>, <floor/wall materials>
+PROPS
+  P1  <object>, <material>, <color>, <size cue>, <state: new/used/half-full…>
+PALETTE
+  3–5 colors, named plainly ("mustard yellow, teal, off-white")
+```
+
+Every entry gets two versions:
+- **FULL** — the whole description, for shots where the whole subject is in frame.
+- **TIGHT** — only what a close-up can see (e.g. `C1-TIGHT: weathered hands, short
+  clean nails, a thin silver ring, sleeves of a faded olive sweatshirt pushed up`).
+
+Close-ups use TIGHT verbatim; wider shots use FULL verbatim. Pasting a whole-person
+description into an ECU of hands drags the rest of the person (and the set) into frame.
+
+## Rules
+
+- 20–35 words per character. Concrete nouns and colors, no adjectives like "beautiful".
+- One **distinctive anchor** per character (a yellow beanie, a scar, round glasses).
+  Anchors survive model drift better than faces do.
+- Avoid real people, brands and logos. Describe the *type* ("a white leather low-top
+  sneaker") not the brand.
+- Props that matter to the story get a state ("a paper cup, lid off, full to the brim
+  with black coffee"). State is what makes the action physically possible.
+- Keep locations simple enough to re-generate: 3 set details, not 12.
+- If the user supplies a reference image, write the bible *from the image* so the text
+  and the image agree.

package/bundled-skills/film-crew/references/roles/script-supervisor.md

@@ -0,0 +1,35 @@
+# Script supervisor
+
+**Job:** protect continuity and catch the shots that will fail *before* anyone spends a
+generation on them. You have veto power: any shot you flag gets rewritten.
+
+## Checklist (run on every shot)
+
+**Continuity**
+- [ ] Every recurring character/prop/location is pasted verbatim from the continuity bible.
+- [ ] Key light direction and color temperature match the rest of the scene.
+- [ ] Screen direction is consistent (subject moving left→right keeps moving left→right).
+- [ ] Props are in the right state (the cup that spilled in S2 isn't full in S3).
+
+**Feasibility**
+- [ ] One subject action, one camera move.
+- [ ] Duration ≤ model max, with handles.
+- [ ] No readable text, logos, UI or signage in frame (unless the model handles text).
+- [ ] Hard physics (liquids, cloth, hands with small objects, multiple people touching) is
+      framed tight, isolated, and given a simple background.
+- [ ] Nothing depends on a specific real person's likeness or a trademark.
+- [ ] Counts are small: "two dogs" works better than "five dogs".
+
+**Unslop** (see `references/unslop.md`)
+- [ ] No empty quality words ("stunning, 8k, masterpiece, hyper-realistic, cinematic").
+- [ ] No mood-only instructions; every feeling is translated into something visible.
+- [ ] Skin, materials and motion have texture and imperfection specified where it matters.
+
+## Output
+
+```
+S2 ⚠️  two actions (pours AND turns to customer) → split into S2a / S2b
+S4 ⚠️  sign text "OPEN" in frame → remove, add in edit
+S3 ✅
+HIGHEST RISK: S2a (liquid physics). Reroll plan: tighten to ECU, lock camera.
+```

package/bundled-skills/film-crew/references/roles/sound.md

@@ -0,0 +1,23 @@
+# Sound
+
+**Job:** plan what the audience hears. Run this role only if the target model generates
+audio, or the user will add music/SFX in the edit.
+
+## Output
+
+```
+MUSIC: <genre, tempo in BPM, energy curve> (added in edit)
+S1 SFX: ceramic clink, café murmur (low)
+S2 DIALOGUE: C1: "Not again." (quiet, deadpan)
+S3 SFX: liquid splash, sneaker squeak
+```
+
+## Rules
+
+- **Audio-capable models:** put spoken lines in double quotes with the speaker named, keep
+  lines under ~8 words per shot, and name 1–2 SFX plus ambience. Too many sound cues
+  produce mush.
+- **Silent models:** don't write sound into the prompt at all. It wastes tokens and can
+  drift the visuals. Put sound in the edit notes.
+- Cut points should land on beats of the music (tell the editor the BPM).
+- Short-form: design for sound-off first. If a line is essential, it also goes in a caption.

package/bundled-skills/film-crew/references/templates/shot-list.md

@@ -0,0 +1,38 @@
+# SHOT LIST — <title>
+
+**Format:** <aspect> · <total length> · target model: <model>
+**Mode:** text-to-video | image-to-video (reference: <file/description>)
+**Brand / product:** <name, or "none given — generic">
+**Logline:** <one sentence>
+
+## Crew notes
+**Director** — intent, hook, beats
+**Production designer** — continuity bible (C1…, L1…, P1…)
+**DP / Gaffer** — look summary in two lines
+**Editor** — timeline summary
+**Sound** — (if applicable)
+**Script supervisor** — flags resolved
+
+## Shots
+| # | Time | Size · Lens · Move | Action (one) | Gen length | Risk |
+|---|---|---|---|---|---|
+| S1 | 0.0–2.5 | ECU · 100mm · locked | … | 4 s | low |
+
+## Prompts
+
+### S1
+```
+<prompt>
+```
+Negative (if supported): `<negative prompt>`
+
+## Edit notes
+- Captions / supers: <text> @ <time>
+- Music / SFX: <cue> @ <time>
+
+## Reroll plan
+| Shot | Likely failure | Change before reroll |
+|---|---|---|
+| S1 | … | … |
+
+**Highest-risk shot:** S? — <why>

package/bundled-skills/film-crew/references/unslop.md

@@ -0,0 +1,29 @@
+# Unslop: why AI video looks like AI video, and what to write instead
+
+| Slop signal | Usual cause in the prompt | Write instead |
+|---|---|---|
+| Plastic, poreless skin | "beautiful", "flawless", "perfect skin" | "visible pores, slight shine on the forehead, faint under-eye shadows" |
+| Everything evenly lit | no light source named | a motivated key ("hard sun through blinds, camera-left") and deep shadows |
+| Floaty slow-motion drift | no speed given, "cinematic" | real-time speed, or a stated speed ("normal speed", "2x slow motion") |
+| Camera wandering aimlessly | no camera instruction | one named move, or "locked-off tripod shot" |
+| Morphing hands / objects | complex hand action, wide framing | tight framing, simple grip, one object, slow action |
+| Faces changing between shots | paraphrased character descriptions | verbatim continuity-bible descriptors, or image-to-video from one reference |
+| Oversaturated, HDR-ish color | "vibrant", "8k", "ultra HD" | a film look ("Kodak Portra 400, soft contrast, fine grain") and a limited palette |
+| Symmetrical stock-footage framing | no composition choice | a lens, an angle and an off-center subject ("subject in left third") |
+| Gibberish text | signage, labels, UI in frame | no readable text in frame; add text in the edit |
+| Nothing actually happens | a mood instead of an action | one visible, physical action with a start and an end |
+
+## Words that add nothing
+
+`stunning, masterpiece, best quality, 8k, 4k, ultra-detailed, hyper-realistic, award-winning, trending, epic, cinematic (alone), breathtaking`
+
+Delete them. They don't hurt much on their own, but they push out words that would help.
+
+## Words that tend to help
+
+- A **lens** (24mm, 50mm, 85mm, macro)
+- A **camera move** (slow push-in, locked-off, handheld)
+- A **light source** (window light, sodium streetlight, overhead fluorescent)
+- A **film stock or look** (35mm film grain, Super 8, VHS camcorder, iPhone front camera)
+- **Imperfection** (scuffed, fingerprints, wrinkled, condensation, frayed)
+- **Real-time physics cues** (splashes, drips, recoils, bounces)

package/bundled-skills/testdriver-e2e-testing/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: testdriver-e2e-testing
+description: "Build E2E tests with TestDriver.ai, the AI code reviewer that runs every pull request in a real desktop sandbox, finds bugs, and builds regression tests"
+category: testing
+risk: safe
+source: community
+source_repo: testdriverai/testdriverai
+source_type: official
+date_added: "2026-09-24"
+author: testdriverai
+tags: [testing, e2e, qa, automation, computer-use]
+tools: [claude, cursor, gemini]
+license: "Apache-2.0"
+license_source: "https://github.com/testdriverai/testdriverai/blob/main/LICENSE"
+---
+
+# TestDriver End-to-End Testing
+
+## Overview
+
+[TestDriver](https://testdriver.ai) is an AI code reviewer that actually runs your app. It automatically runs every pull request in a real desktop sandbox, finds bugs, and builds regression tests. Tests control browsers and native applications using natural language element descriptions and AI vision, and run as Vitest suites. This skill teaches an agent how to author, run, and debug TestDriver tests.
+
+## When to Use This Skill
+
+- Use when you need to write an end-to-end test for a web or desktop application
+- Use when automating a UI workflow that has no stable selectors (canvas, Electron, native apps)
+- Use when the user asks to verify that a page or flow works ("check if the login page works")
+- Use when debugging a failing TestDriver test
+
+## How It Works
+
+### Step 1: Set up the project
+
+```bash
+npx testdriverai init
+```
+
+This scaffolds `package.json`, example tests, `vitest.config.mjs`, and a GitHub Actions workflow. The user must set `TD_API_KEY` in `.env` (get a key at https://console.testdriver.ai/team).
+
+### Step 2: Write a test
+
+Tests are Vitest suites using the TestDriver hooks:
+
+```javascript
+import { describe, expect, it } from "vitest";
+import { TestDriver } from "testdriverai/vitest/hooks";
+
+describe("Login", () => {
+  it("signs in successfully", async (context) => {
+    const testdriver = TestDriver(context);
+    await testdriver.provision.chrome({ url: "https://example.com/login" });
+
+    const email = await testdriver.find("email input field");
+    await email.click();
+    await testdriver.type("user@example.com");
+
+    const submit = await testdriver.find("Sign In button");
+    await submit.click();
+
+    const result = await testdriver.assert("the dashboard is visible");
+    expect(result).toBeTruthy();
+  });
+});
+```
+
+### Step 3: Run and iterate
+
+```bash
+vitest run tests/login.test.mjs
+```
+
+Screenshots are captured automatically before and after every command and saved to `.testdriver/screenshots/`, named with the source line number for easy debugging.
+
+## Examples
+
+### Example 1: Testing a desktop (Electron) app
+
+```javascript
+await testdriver.provision.electron({ appPath: "./dist/my-app" });
+const menu = await testdriver.find("File menu in the menu bar");
+await menu.click();
+```
+
+### Example 2: Waiting for slow elements
+
+```javascript
+const done = await testdriver.find("Loading complete indicator", { timeout: 30000 });
+await done.click();
+```
+
+## Best Practices
+
+- ✅ Use specific element descriptions ("blue Sign In button in the header", not "button")
+- ✅ Set both `testTimeout` and `hookTimeout` to 900000 in `vitest.config.mjs`
+- ✅ Add `assert()` calls for verifiable pass/fail conditions
+- ✅ Always `await` every TestDriver call
+- ❌ Do not use `npx vitest`; run `vitest run` directly
+- ❌ Do not rely on CSS selectors; TestDriver locates elements visually
+
+## Limitations
+
+- Requires a TestDriver API key (`TD_API_KEY`) and network access to provision sandboxes.
+- Only works with Vitest as the test runner.
+- This skill does not replace environment-specific validation, testing, or expert review.
+
+## Security & Safety Notes
+
+- `npx testdriverai init` writes project files to the current directory; run it only in a project you intend to modify.
+- The `TD_API_KEY` credential belongs in `.env` (gitignored by the scaffold). Never commit it.
+- Tests execute inside an isolated remote sandbox, not on the local machine.
+
+## Common Pitfalls
+
+- **Problem:** Cleanup hooks fail with a 10s timeout.
+  **Solution:** Set `hookTimeout: 900000` in `vitest.config.mjs`; sandbox teardown and recording uploads take longer than Vitest's default.
+- **Problem:** Scrolling does nothing.
+  **Solution:** An input field has focus. Press Escape or click the page background first, then scroll.
+
+## Related Skills
+
+- `@webapp-testing` - Playwright-based alternative for local web apps with stable DOM selectors

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "4.0.73",
+  "version": "4.0.74",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills_index.json

@@ -22486,6 +22486,39 @@
       "reasons": []
     }
   },
+  {
+    "id": "film-crew",
+    "path": "skills/film-crew",
+    "category": "media",
+    "name": "film-crew",
+    "description": "Turn a one-line AI video idea into a shot list and per-shot, model-ready prompts via a film crew (director, DP, gaffer, editor, script supervisor). Also fixes failing video prompts and diagnoses bad clips before a reroll. Works with Wan, LTX, Kling, Veo, Seedance, Hailuo, Runway.",
+    "risk": "safe",
+    "source": "https://github.com/HEOJUNFO/ai-film-crew/tree/533f61be2741c10932c6c86e47777cac9ffe3fe4/skills/film-crew",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "official",
+    "source_repo": "HEOJUNFO/ai-film-crew",
+    "license": "MIT",
+    "license_source": "https://github.com/HEOJUNFO/ai-film-crew/blob/533f61be2741c10932c6c86e47777cac9ffe3fe4/LICENSE",
+    "tags": [
+      "video",
+      "text-to-video",
+      "shot-list",
+      "prompting",
+      "film"
+    ]
+  },
   {
     "id": "find-bugs",
     "path": "skills/find-bugs",
@@ -36412,6 +36445,39 @@
       "reasons": []
     }
   },
+  {
+    "id": "mcp-dependency-drift-audit",
+    "path": "skills/mcp-dependency-drift-audit",
+    "category": "security",
+    "name": "mcp-dependency-drift-audit",
+    "description": "Statically audit MCP configs for mutable npm/npx package references before approval or CI, without executing discovered MCP servers.",
+    "risk": "safe",
+    "source": "https://github.com/tomelias10/mcp-drift-check",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "community",
+    "source_repo": "tomelias10/mcp-drift-check",
+    "license": "MIT",
+    "license_source": "https://github.com/tomelias10/mcp-drift-check/blob/v0/LICENSE",
+    "tags": [
+      "mcp",
+      "ai-security",
+      "supply-chain",
+      "devsecops",
+      "sarif"
+    ]
+  },
   {
     "id": "mcp-server-security",
     "path": "skills/mcp-server-security",
@@ -39102,6 +39168,137 @@
       "research"
     ]
   },
+  {
+    "id": "nexrad-mosaic-access",
+    "path": "skills/nexrad-mosaic-access",
+    "category": "data",
+    "name": "nexrad-mosaic-access",
+    "description": "Access official NOAA/NCEP MRMS radar and multisensor composites for a region and time; validate product, grid, domain, quality, timestamp, and provenance.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "self",
+    "tags": [
+      "weather",
+      "nexrad",
+      "mrms",
+      "mosaic",
+      "qpe",
+      "vil",
+      "vii",
+      "mesh",
+      "composite-products"
+    ]
+  },
+  {
+    "id": "nexrad-mosaic-construction",
+    "path": "skills/nexrad-mosaic-construction",
+    "category": "analysis",
+    "name": "nexrad-mosaic-construction",
+    "description": "Construct a quality-aware NEXRAD multi-radar mosaic from aligned single-site products with explicit coverage, beam geometry, quality weighting, overlap resolution, and provenance.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "self",
+    "tags": [
+      "weather",
+      "nexrad",
+      "mosaic",
+      "multi-radar",
+      "quality-weighting",
+      "coverage",
+      "overlap-resolution"
+    ]
+  },
+  {
+    "id": "nexrad-product-access",
+    "path": "skills/nexrad-product-access",
+    "category": "data",
+    "name": "nexrad-product-access",
+    "description": "Discover and access NEXRAD data for a selected radar site, time, product, or Level II moment using completed archive volumes, real-time chunks, or supported Level III sources with metadata validation.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "self",
+    "tags": [
+      "weather",
+      "nexrad",
+      "level-ii",
+      "level-iii",
+      "radar-products",
+      "single-site",
+      "aws-s3"
+    ]
+  },
+  {
+    "id": "nexrad-radar-visualization",
+    "path": "skills/nexrad-radar-visualization",
+    "category": "analysis",
+    "name": "nexrad-radar-visualization",
+    "description": "Plot NEXRAD Level II/III site scans and decoded radar mosaics with correct radar geometry, map grids, units, quality masks, timestamps, and provenance.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "self",
+    "tags": [
+      "weather",
+      "nexrad",
+      "radar-plotting",
+      "ppi",
+      "velocity",
+      "dual-pol",
+      "cross-section",
+      "visualization"
+    ]
+  },
   {
     "id": "nextjs-app-router-patterns",
     "path": "skills/nextjs-app-router-patterns",
@@ -45046,6 +45243,40 @@
       "coaching"
     ]
   },
+  {
+    "id": "radar-satellite-analysis",
+    "path": "skills/radar-satellite-analysis",
+    "category": "analysis",
+    "name": "radar-satellite-analysis",
+    "description": "Interpret weather radar and satellite observations by validating product metadata and geometry, deriving storm and cloud structures, tracking evolution, and quantifying uncertainty.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-09-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "self",
+    "tags": [
+      "weather",
+      "radar",
+      "satellite",
+      "nexrad",
+      "goes",
+      "nowcasting",
+      "storm-analysis",
+      "remote-sensing",
+      "uncertainty"
+    ]
+  },
   {
     "id": "radare2",
     "path": "skills/radare2",
@@ -54070,6 +54301,39 @@
     "source_type": "community",
     "source_repo": "amElnagdy/guard-skills"
   },
+  {
+    "id": "testdriver-e2e-testing",
+    "path": "skills/testdriver-e2e-testing",
+    "category": "testing",
+    "name": "testdriver-e2e-testing",
+    "description": "Build E2E tests with TestDriver.ai, the AI code reviewer that runs every pull request in a real desktop sandbox, finds bugs, and builds regression tests",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-09-24",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "official",
+    "source_repo": "testdriverai/testdriverai",
+    "license": "Apache-2.0",
+    "license_source": "https://github.com/testdriverai/testdriverai/blob/main/LICENSE",
+    "tags": [
+      "testing",
+      "e2e",
+      "qa",
+      "automation",
+      "computer-use"
+    ]
+  },
   {
     "id": "testing-patterns",
     "path": "skills/testing-patterns",