What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Specification Status Reveal

When to use

• You're reviewing a product and the spec table is doing the real persuading — battery, weight, ports, warranty — but a static table makes viewers' eyes glaze over
• You're comparing two or three products and want the audience to see, row by row, where each one wins or fails instead of dumping three tables at once
• Your video walks through a requirements checklist (does it meet the spec?) and each row needs its own moment of suspense
• You're presenting test results where some specs passed, some failed, and some need a footnote — and the mix is the story
• You want a repeatable spec-reveal style across reviews so returning viewers instantly know how to read your verdicts

Workflow

1. Write the spec rows (input: product specs + test results → output: spec table)
   Build the table as rows, one spec per row: spec name, claimed value, measured or verified value, status. Keep it to 5–9 rows — the specs that decide a purchase, not every line from the datasheet. Cut anything the audience can't act on ("operating humidity 10–90%") unless the video is specifically about it. Each row gets a status now, before animating: pass, fail, partial, or untested. No row ships with a status you haven't verified — "untested" is an honest status, a guessed "pass" is a lie with a green checkmark.
2. Order the rows for drama (input: spec table → output: ordered reveal sequence)
   Order the rows so the reveal builds: open with one easy pass to establish the rhythm, alternate pass and fail through the middle, and put the most decision-relevant row last — the battery life, the price, the one spec the audience actually buys on. Never group all the fails together at the end unless the product genuinely collapses; a clump of red at the end feels like an ambush, while fails spread through the sequence feel like honest evaluation. If you're comparing products, reveal the same row across all products before moving to the next row — row-by-row comparison beats product-by-product dumps.
3. Stage the "checking" state (input: ordered rows → output: checking-state layout)
   Every row starts in a "checking" state: spec name visible, value area showing a pulsing placeholder (three animated dots or a shimmering bar), status area empty. The checking state is what creates the suspense — the audience watches a row get evaluated instead of reading a finished table. Placeholder animation: a 1.2s shimmer loop, subtle enough to read as "working," never as a loading spinner that suggests the video is buffering. Keep the checking state on screen for 0.6–1.2s per row before the reveal; shorter feels fake, longer feels slow.

Template preview

Specification Status Reveal — Spec Table Template

One table per product (or one table, same rows across products for comparisons).

Product: {name} | Verdict line: {one sentence, no single-number verdict}

Spec rows (5–9, in reveal order)

Reveal order rule: one easy pass first, most decision-relevant row last. Comparisons: reveal the same row across all products before moving on.

Animation timing (per row)

Status marks: {pass = check · fail = cross · partial = half-mark · untested = dash — shape, never color alone} Accumulation: {revealed rows stay visible; full table present by final row}

Closing tally

Buy the full skill pack — $4.99 Pro — all 471 skills