Skip to content

mehbylabs/creator-skills / skills/creator-explainer

creator-explainer

Flagged

Turn a topic, article, notes, or document into a narrated explainer video — script, voiceover, per-scene visuals, music bed, captions, final MP4 — using whatever providers the user has, and degrading gracefully (video clips → animated stills → captioned slideshow). Use when the user asks for an explainer, faceless video, narrated video, YouTube video from an article, educational video, listicle video, or "turn this into a video". Not for single clips (creator-video) or product ads (creator-ad).

FileKindSize
SKILL.mdskill md4.1 KB
references/arabic-voice.mdmarkdown7.7 KB
references/audio.mdmarkdown3.4 KB
references/browser-aistudio-browser.mdmarkdown2.8 KB
references/browser-flow-browser.mdmarkdown4.5 KB
references/browser-gemini-browser.mdmarkdown4.8 KB
references/config.mdmarkdown2.5 KB
references/connect.mdmarkdown3.9 KB
references/explainer-structure.mdmarkdown1.4 KB
references/image-prompting.mdmarkdown1.7 KB
references/media-ops.mdmarkdown2.4 KB
references/providers.mdmarkdown7.0 KB
references/video-prompting.mdmarkdown1.9 KB
scripts/connect.pyexecutablescript16.6 KB
scripts/creator.pyexecutablescript71.1 KB
scripts/media.pyexecutablescript15.7 KB

references/explainer-structure.md

View on GitHub
# Explainer structure

## Shape

1. **Hook (0–5 s)** — a question, surprising fact, or stakes. No greetings, no "in this video".
2. **Context (1 beat)** — why it matters to *this* audience.
3. **Core beats (2–5)** — one idea each, concrete example per beat, plain words.
4. **Payoff** — the takeaway in one sentence.
5. **CTA (optional)** — one action, ≤ 1 sentence.

## Pacing

| Length | Words | Scenes |
|---|---|---|
| 30 s (Short) | 70–80 | 4–6 |
| 60 s | 140–160 | 6–9 |
| 90 s | 210–240 | 8–12 |
| 3 min | 420–480 | 15–20 |

- Change the visual every 3–6 s on vertical, 5–10 s on 16:9.
- One sentence ≈ one visual idea. If a sentence needs two visuals, split it.

## Writing for voice

- Short sentences; active voice; second person ("you").
- Numbers: round and contextualize ("about one in four", not "24.7%") unless precision is the point.
- Avoid parentheses, lists read aloud, and URLs.

## Accuracy

- Every factual claim must come from the user's source or be common knowledge; flag
  anything uncertain in the script for the user to verify before voicing.
- Don't invent quotes, statistics, or studies.

## Scene table template (`script.md`)

| # | Narration | Visual | On-screen text |
|---|---|---|---|
| 1 | Why does the sky turn red at sunset? | Wide sunset over ocean, warm orange sky | — |
| 2 | Sunlight travels further through air… | Diagram-like illustration of light path through atmosphere | "Longer path" |
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