Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Render Whiteboard Explainer

ASecurity

Assemble a whiteboard explainer video ad from a beats file — a narrator explains one idea while a real whiteboard fills up in black marker, with a hand-lettered title, bulleted rows down the left, a drawing filling the right, and a payoff that letters the closing line and rings the claim. The board is a PHOTOGRAPH and the ink is multiplied onto it, so the surface sheen and window light come through the strokes; the drawings are generated as line art and traced to ordered strokes, then reveale...

1,232 stars
0 votes
0 copies
0 views
Added 10/2/2026
ai-agentsgoaws

Works with

cli

Security Analysis

A100/100

Pro scans all 15 files and shows the line behind each finding

Scanned 10/2/2026

$npx -y skills add gooseworks-ai/goose-skills --skill render-whiteboard-explainer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Render Whiteboard Explainer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Render Whiteboard Explainer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gooseworks-ai-render-whiteboard-explainer/badge)](https://www.skillsdirectory.com/skills/gooseworks-ai-render-whiteboard-explainer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: render-whiteboard-explainer
description: Assemble a whiteboard explainer video ad from a beats file — a narrator explains one idea while a real whiteboard fills up in black marker, with a hand-lettered title, bulleted rows down the left, a drawing filling the right, and a payoff that letters the closing line and rings the claim. The board is a PHOTOGRAPH and the ink is multiplied onto it, so the surface sheen and window light come through the strokes; the drawings are generated as line art and traced to ordered strokes, then revealed in drawing order on the word they belong to. The layout is SOLVED from the beats, never hand-placed. FREE assembly (Pillow plus ffmpeg) apart from one board photo and one drawing per subject, both one-time per brand. Use for the whiteboard format.
status: draft
---

# render-whiteboard-explainer

The renderer for the **whiteboard** video ad format: a voice explains one idea while a board
fills up in marker, the way a graphic recorder works a room. Every mark lands on the word it
belongs to, and the board is wiped and reused between sections.

Siblings in the chat-UI family are `render-imessage-chat`, `render-chatgpt-chat` and
`render-apple-notes-chat`, where a screen is the creative. Reach for this one when the creative
is **someone explaining a thing by drawing it**.

## The three decisions that make this format work

**The board is a photograph.** A drawn board reads as a drawn board, and a plain white frame
reads as a sketch film. Both were built and both were rejected. One generated still of a real
blank whiteboard in a real room is the plate, and the ink is multiplied onto it so the surface
sheen and the window light come through the strokes rather than sitting on top as flat black.
The handheld drift is generated over both layers at once, so nothing can slide against anything.

**The drawings are generated as line art, then traced.** Do not hand-code them, and do not trace
painterly images. Art traced from a photograph carries every contour the photograph had and
reads as clip-art; art generated as a marker drawing traces to a handful of confident paths. An
open hand came back as a single continuous stroke. Chain each generation off the first so the
line weight matches across the set.

**There is no colour.** Black marker throughout. Do not add an accent.

## Choices

The recipe asks these before any paid step; this renderer only draws what the beats say.

- **the script** — what the narrator says. Everything downstream is anchored to its word
  timings, so it is settled first and never changed afterwards.
- **the beats** — for each moment, what is SAID and what is DRAWN. A row of text, a drawing, or
  both. One number can be marked as the hero, which letters it large instead of as another row.
- **the title and subtitle** — lettered on the first board.
- **the payoff** — the closing line, lettered on the last board, with a ring closing around the
  claim it refers to.
- **the boards** — how many times the board is wiped and reused. Three suits a half-minute.

Brand facts come from the brand kit.

## What it renders

1. **The plate.** One photograph of a blank board in a room, generated once per brand, then
   cropped so the board fills the frame with its side edges running out of shot. The writable
   surface is measured off the image and pulled inside the caption safe zone before anything is
   mapped through it.
2. **The drawings.** One black line drawing per subject the script names, generated once per
   brand and traced into ordered stroke paths.
3. **The layout.** Solved from the beats, not authored. Rows go down a left column, drawings
   down a right one, with an enforced gutter between them, and the content runs the full height
   of the board. Boards are split at a pause near a balanced boundary, which is where a person
   would wipe.
4. **The video.** Marks appear stroke by stroke in drawing order, each starting on its own word.
   Text is written letter by letter. The board wipes between sections. Captions sit inside the
   safe zone and never run ahead of the voice.
5. **The master.** Gentle compression before a measured two-pass loudness normalisation, then a
   limiter. Targets minus fourteen LUFS with true peak under minus one and a half, and keeps the
   payoff hold intact.

## Non-negotiables

- **Every mark lands on its own word.** The voiceover is the clock. An anchor that resolves to
  the wrong word does not look wrong, it silently reorders the video: one that matched an early
  word instead of a late one once dragged a whole section to the front, and the ad played its
  ending first with nothing reporting a problem. Anchors are resolved once, shared by the solver
  and the renderer, and an ambiguous one is refused rather than guessed at.
- **Nothing is hand-placed.** Anything that refers to something else — an arrow, a note, a
  ring — takes its target as an argument and works out its own position. Anything sharing space
  with a drawing is bounded by that drawing's box. Two things placed at coordinates chosen
  independently will eventually meet.
- **Copy a reference's grammar, never its content.** The reference board bullets its rows with
  a drawn eye and fans emphasis marks beside its phrases, but those belong to that board's
  brand. Reproduced on another script they are decoration that means nothing. Filler has to be
  about something: a drawing of what the line refers to, never abstract specks.
- **Two reviews, both human.** The storyboard still costs seconds and is where relevance is
  judged — whether a mark is about the line it sits under, whether the payoff says the closing
  line. No automated check decides that. Then the finished cut, watched end to end with the
  `watch` skill.

## Inputs

- the spoken audio and its **word-level timings**, as described below
- a beats file — see the example beside the scripts
- a brand kit for the facts

**The voice comes with its word timings.** `create-vo-elevenlabs` returns audio only, and this
format needs a timing for every word. `scripts/gen-voice.py --project <dir>` reads `vo` and `voice`
from `beats.json` and calls the proxy's `/with-timestamps` route, writing `voice/vo.mp3` and
`voice/words.json`, which `make-episode.py` requires. A dry run prints the character count and the
cost; `--yes` spends. It routes through the GooseWorks proxy (`scripts/media_proxy.py`), never the
speech provider directly, and refuses a payload it has already paid for.

## Checks it runs itself

The build refuses to continue when any of these fail, and names what broke:

- every anchor resolves to exactly one intended word
- sections start in script order
- every mark finishes being drawn before its board is wiped
- rows stay inside the column and cannot reach a drawing
- loudness, true peak and the payoff hold

## Cost

The board photo and the drawings are **one-time per brand**. A second video for the same brand
costs only the voiceover. Everything else — the layout, the lettering, the tracing, the render
and the master — is free and local. Rendering a half-minute takes under three minutes.

## Honest ceiling

Measured against the filmed reference this reaches about a fifth of its ink cover, because the
reference is a time-lapse of a much longer drawing session while every mark here waits for its
word. Filler narrows that and does not close it. If a brief needs a genuinely full board, the
script has to be longer or the marks have to stop waiting for words.

Attribution

gooseworks-aigooseworks-ai
View sourceSee grades on GitHubMore from gooseworks-ai →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →