Index of every page on this site: llms.txt
All skills
hktitan avatar

/khe-launch-film

@945e23c
by Harshit Khemanihktitan/skills47 stars
2
Run it yourself

Plans, cuts and reviews a product launch video against 47 measured films: writes the brief and finds the one moment the film must show, names the register, then times the beats, on-screen type, UI demo, shot motion, seams and cuts, and judges a render at native fps against its own register's numbers. Use when someone wants a launch film, sizzle, teaser, README film, logo sting, landing-page loop or a 9:16 cut, says "review my launch video", "what should the video show", "it looks good but people don't get it", "it feels like a slideshow", "when should the name appear", "how fast should the prompt type", or hands over a reference film to measure. For the soundtrack once picture is locked use `khe-sound`; for motion inside the product use `khe-ui`; for a faux UI demo on a page use `stageshow`.

Use this Skill: https://skilld.dev/gh/hktitan/skills/khe-launch-film

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

README.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

khe-launch-film

Plan, cut, score and review a launch video against 47 measured films.

npx skills add HKTITAN/skills --skill khe-launch-film

What it does

  • Starts from a five-line brief: who is watching, what they should believe, the one moment the film must show and the real file behind it.
  • Names the film's register and takes every pacing number from that row of 47 measured films; picks the story structure by the question the viewer is asking.
  • Times the beats: first word, first seam, when the name lands, the payoff and the endcard.
  • Sets the on-screen type, the UI demo, shot motion, seams and cuts with measured values.
  • Reviews a render at native fps against its own register and reports each miss with its frame, then checks with a cold viewer that the moment landed.

When to use it

Reach for it when you are planning a launch film, sizzle, sting, loop or vertical cut and want the pacing decided by measurements, or when a render feels off and you cannot say why. It tells you what kind of film you are making, when the name should land, how fast words and prompts should arrive, and where a cut is allowed. It also measures a reference film before you copy its numbers into a brief.

Invoke with

/khe-launch-film [plan | review | formats] [target]

Or describe the problem in your own words. The skill's description carries the triggers, so no special wording is needed.

Before and after

Before: no register named; sentences fade in as blocks; an unknown product's name is held to 70 % of the film; cuts land on settled frames; the endcard shows a bare URL.

After: UI motion at about 4 cuts a minute and 9 % still; a readable word by 0.2 s; the name at 29 % where the problem act ends; words built 0.2 s apart and held 1.15 s; a 5.0 s endcard whose last 2.0 s hold still.

Example prompts

  • I'm making a 60 second launch video for a dev tool nobody has heard of. When should the name show up?
  • Here's my render. It feels like a slideshow and I can't tell why.
  • I need a 9:16 version of our launch film for the feed. Can I just crop it?

Pairs with

  • khe-sound: this skill only names the sound register and its loudness; the cue sheet, the track placement and the files are built there, after picture lock.
  • khe-ui: a film's 0.5 s entries and long holds are wrong for product UI, so anything that ships in the product is timed there.
  • stageshow: the product surface a shot shows is built as a faux demo first, framed and checked frame by frame, before the film crops into it.
  • khe-ui: review findings use its Before, After, Why table, one issue per row.

Verify

node scripts/film-check.mjs plan.json --gate
node scripts/film-check.mjs plan.json render.mp4 --gate
node scripts/film-check.mjs --self-test

The gate reads a film plan (JSON), a beat sheet or a review (markdown) and names every fault as a line, such as beat-gap:, name-window: or cut-rate:. It ends film check passed only when every never-intentional line is at 0. With ffprobe on PATH and a video passed beside the plan, it also holds the file's duration, frame rate, size, H.264 level and frame count to the plan; without ffprobe it prints inconclusive: ffprobe not found and still checks the plan.

What it proves: when the plan carries a brief, its moment sits on a beat of at least 1.5 s with a real source, the plan names one register, its beats cover the runtime, the name, the endcard, the cut rate and the still share sit inside that register's measured numbers, every seam is typed, type can be read, and no sound is placed before picture lock.

What it does not prove: that the film is worth watching. It reads no pixel, counts no cut on a render and hears no sound. Those are answered from frames in references/verify.md and by a fresh-eye review. Passing is necessary, not sufficient.

What is inside

  • SKILL.md: the one idea, the workflow with its exits, the rules and the reference index.
  • references/: 23 references the agent opens one at a time (among them brief.md, structures.md, verify.md, review.md and sources.md), plus gotchas.md and pov.md, which are yours to edit.
  • examples/: the gold. Three film plans in three registers, one beat sheet and one finished review.
  • teaching/: fifteen bad/good pairs, one folder per gate line, the same plan twice with one thing wrong.
  • scripts/film-check.mjs: the gate. Zero dependencies, Node 20 or later.
  • LICENSE: MIT.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning4d3 checks · Risk SAFE
  • Gen Agent Trust Hub4d

    This skill provides a professional framework for planning and verifying product launch videos using measured data from 47 films. It includes detailed reference guides, example plans, and a verification script for metadata extraction. The skill maintains a strong security posture by requiring explicit user approval for network operations and using safe execution methods for its local verification tools.

  • Socket4d

    No alerts

  • Snyk4d

    Risk: MEDIUM · 2 issues

Signed by skilld at 945e23c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
metadata
{
  "author": "Harshit Khemani",
  "version": "1.0.0"
}

README badge

README badge for hktitan/skills/khe-launch-film