vawe-type-explainer

Plans explainer video scenes with counted facts and payoff-last beat structure for the Vawe engine.

3|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Vandit1604/vawe --skill vawe-type-explainer-vandit1604
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vawe-type-explainer
Source: https://github.com/Vandit1604/vawe/tree/main/skills/vawe-type-explainer
Command: npx skills add https://github.com/Vandit1604/vawe --skill vawe-type-explainer-vandit1604

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authoring an explainer video in the Vawe engine requires choosing the right beat structure, pacing, and motion devices so facts land clearly without a product or site to show. This Skill provides the playbook for that video type, including when to use a single continuous action versus a multi-beat spine. ## Core Features & Use Cases - Length-adaptive spine: Under ~15s it switches to one continuous action (a held counted figure); at or past 15s it composes a hook -> build -> counted proof -> payoff beat structure with a 2.5-4.0s pace band. - Real counted figures: Enforces real, checkable numbers via the count layer, with automatic compaction for values >= 1e6, and requires the most surprising fact to land last. - Motion and scaffold guidance: Maps each beat role to named motion devices (kineticHook, containerFill, statReveal, wordBlast) and supports make scaffold TYPE=explainer DUR=<n> to generate the scene JSON. - Use Case: Ask the agent to turn a data-driven article into a 20-second 16:9 explainer video; it scaffolds the scene, orders beats so the payoff lands last, and keeps the pace quiet enough for facts to be read. ## Quick Start Use the vawe-type-explainer skill to plan a 20-second explainer video about this topic with real counted figures and the payoff saved for the final beat.

Frequently Asked Questions about vawe-type-explainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an explainer video with the Vawe engine?

Run make scaffold with TYPE=explainer and a DUR value to generate the scene JSON. Under 15 seconds it produces one continuous counted action; at 15 seconds or more it composes a hook, build, counted proof, and payoff beat spine.

How long should each beat be in an explainer video?

Explainer beats use a 2.5-4.0 second pace band, held longer than launch or demo films. The goal is to let one idea land before the next starts, since motion is a cost the viewer pays to keep reading.

Does an explainer video need product screenshots or captured assets?

No captured assets are required. An explainer is built from type, counts, and named-thing chips rather than captured UI, making it the fastest type to validate clean out of the box at 15 seconds or more.

When should I use a continuous action instead of the multi-beat spine?

Use a continuous action when the film is under roughly 15 seconds. A single held figure counting up from zero to its final value is one continuous action, and forcing the four-beat build into 10 seconds is discouraged.

Why must the payoff come last in an explainer video?

Ordering beats so the most counterintuitive fact lands at the very end keeps the hook from spoiling the surprise. The judge for this type specifically weighs whether the payoff is the most surprising fact and whether it lands last.