Pesty explainer

Produce a finished, Pesty-branded explainer video from a single request, with no routine check-ins: the user expects an MP4 back. Honor an explicit script, storyboard, or shorter-clip request. Missing credentials or material source gaps require a focused clarification; never invent them. It runs the same proven pipeline as the animated-explainer skill (script → ElevenLabs voice → Manim → QA → assembly) with three differences that matter:

1. Audience and voice. The viewer is a pest control operator (PCO), usually an owner doing $1M–$20M who wants to grow. Pesty talks to them operator-to-operator: confident, plain-spoken, specific, a little scrappy. See references/pesty-voice.md.
2. Proof. Pesty leads with real numbers, so the video usually lands one or two of them. Every number must be real and sourced. An invented stat in a marketing video is a liability for the brand.
3. The look. Pesty's web design system translated to motion: white canvas, deep-teal ink, Pesty Red only as a spotlight, Epilogue headlines, the mark in the corner, and a logo end card with one CTA. See references/pesty-style.md and assets/reference.png.

For a script or storyboard request, complete the proof and storyboard steps and deliver those artifacts; skip runtime setup, credentials, narration, and rendering.

Pipeline at a glance

storyboard.json --tts.py--> audio + timings.json --scenes.py (Manim + pesty.py)--> rendered acts
     --frames.py--> visual QA stills --assemble.py--> explainer.mp4 + captions.srt

This skill requires animated-explainer (its scripts and rendering engine). Install both with: