Skip to content

ericrisco/rsc-harness / skills/vsl-script

vsl-script

Verified

Use when writing or revising a spoken sales video with timed narration, visual cues, supported claims and one next action. NOT writing the surrounding page (that is `landing-copy`) or rendering the video (that is `remotion-video`).

FileKindSize
SKILL.mdskill md6.5 KB
evals/README.mdmarkdown1.8 KB
evals/cases.yamlconfig3.7 KB
references/storyboard-handoff.mdmarkdown2.3 KB

references/storyboard-handoff.md

View on GitHub
# Make the script filmable

Use this reference when the script will go to an editor, presenter or animation tool. Keep a single
script record; a storyboard is a view of the approved narration, not another independently edited offer.

## Scene contract

For each scene, give the editor:

- **Time:** elapsed start/end and whether speech overlaps the visual.
- **Narration:** exact spoken words, or an explicit silent interval.
- **Screen:** the action to capture and the minimum readable text.
- **Evidence:** source ID, permitted use and the particular claim supported.
- **Asset:** existing file/link, capture needed, or unresolved permission.
- **Transition:** the visual or verbal connection to the next scene.

For example, a booking-app scene could show a real test account selecting an available slot and
receiving confirmation. Its evidence is the recorded behavior. It does not establish an average
time saving. Use test data and conceal personal customer information in the capture.

## Production decisions

Ask about aspect ratio, placement, presenter and visual style only when these are needed and not
already supplied. A landing embed may need readable interface crops rather than a full desktop
recording. If no assets exist, mark capture tasks; a proposed screenshot is not an available asset.

Provide captions matching the spoken words and a transcript for the surrounding page. Important
visual-only information needs a text or audio equivalent. Account for this in the timing instead of
adding narration after the budget is closed. A silent demo can retain its silence with concise,
readable captions and a descriptive transcript.

List production dependencies in execution order: verify offer and permitted claims, collect assets,
record or synthesize approved narration, assemble scenes, review readable text and captions, then
test the actual playback and destination. Respect the user's chosen production tools and existing
authorization; a script request does not authorize buying assets or publishing a video.

Before handoff, compare the narration and end card against the linked offer revision. If the offer
changes after recording, identify affected scenes and page text together. Record what is ready,
what needs capture and what requires approval; never label the unrendered storyboard a finished film.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall