Skip to content

sprezzature-video

Video claims

A README gets re-read. A number burned into a keyframe does not. This package holds a film’s assertions against the code they describe, in both directions, and answers whether the film can be rendered again at all from a clean clone.

SKILL.md (the agent spec) Give a ⭐️ on GitHub

Makes

  • WebVTT from the narration script and the measured length of each audio file, not from a transcript and not typed by hand
  • A poster baked as frame zero, because Slack, X and Discord regenerate their thumbnail server-side from the first frame whatever a poster= attribute says
  • Loudness normalised across a series, so one film is not louder than the next

Audits

  • verify — every declared claim against the file that would have to change for it to stop being true
  • scan — every number visible on screen that no claim accounts for, because the dangerous claim is the undeclared one
  • pitch — problem, then solution, then underlying magic, in Guy KAWASAKI’s order, with a feature list refused where an insight belongs
  • assets — can this film be rendered again from a clone? Tracked, derived, or exists in exactly one place
  • prose — the on-screen writing against the project’s charter, one finding per line

Say one of these

The skill triggers itself on phrasing like this, no command to memorize.

make a launch video the demo video is out of date verify the claims in this video re-cut the film is this number still right can we rebuild this video poster frame

Reference library

The knowledge the skill draws on: read them straight from the repo.

Where it stops Every trigger phrase