Skip to content
Skills Library
Marketing & content · Conversion & formats

evidence-explainer

/evidence-explainer

Turn a voice note or audio clip (no camera footage needed) into a ~1-minute vertical explainer for TikTok / Reels / Shorts that PROVES what the speaker says - full-screen screenshots of real websites zoomed onto the exact line (with highlighter), company logos stamped in with a camera click, a step-by-step architecture diagram a lay person can follow, plain-English cards for every jargon word, a "ka-ching" on every successful money/transaction step, a hook first and a follow CTA last, word-by-word subtitles anchored to the bottom. Use whenever someone shares an audio recording / voice memo / p

Author
liwoo ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

87/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability17 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turn a voice note or audio clip (no camera footage needed) into a ~1-minute vertical explainer for TikTok / Reels / Shorts that PROVES what the speaker says - full-screen screenshots of real websites zoomed onto the exact line (with highlighter), company logos stamped in with a camera click, a step-by-step architecture diagram a lay person can follow, plain-English cards for every jargon word, a "ka-ching" on every successful money/transaction step, a hook first and a follow CTA last, word-by-word subtitles anchored to the bottom. Use whenever someone shares an audio recording / voice memo / p

Triggers from the description

ka-ching
Original author description

Turn a voice note or audio clip (no camera footage needed) into a ~1-minute vertical explainer for TikTok / Reels / Shorts that PROVES what the speaker says - full-screen screenshots of real websites zoomed onto the exact line (with highlighter), company logos stamped in with a camera click, a step-by-step architecture diagram a lay person can follow, plain-English cards for every jargon word, a "ka-ching" on every successful money/transaction step, a hook first and a follow CTA last, word-by-word subtitles anchored to the bottom. Use whenever someone shares an audio recording / voice memo / p

How it works

  1. Setup
  2. The stages (read the reference when you get there)
  3. House style (from the creator's review of the first video — keep it unless told otherwise)
  4. Checkpoints (stop and ask, with a recommendation)
  5. Working principles
  6. Final summary format
Original SKILL.md headings · 74 lines, 1,079 words
SKILL.md preview
---
name: evidence-explainer
description: Turn a voice note or audio clip (no camera footage needed) into a ~1-minute vertical explainer for TikTok / Reels / Shorts that PROVES what the speaker says - full-screen screenshots of real websites zoomed onto the exact line (with highlighter), company logos stamped in with a camera click, a step-by-step architecture diagram a lay person can follow, plain-English cards for every jargon word, a "ka-ching" on every successful money/transaction step, a hook first and a follow CTA last, word-by-word subtitles anchored to the bottom. Use whenever someone shares an audio recording / voice memo / podcast snippet / mp3 / m4a and asks for a TikTok, short, reel, explainer, "1 minute video", "video with evidence / receipts / sources / screenshots", "show the websites", "add logos", "make it easy for a lay person", or wants to explain how a product, fintech, payment flow, app or company works behind the scenes. Also for re-cutting or restyling an explainer made this way (zooms, sounds, logos, subtitles). Not for editing filmed talks or piece-to-camera footage (this builds the picture from evidence, not from a camera).
---

# Evidence explainer (voice note → 1-minute vertical video with receipts)

Built on "How Malawians get Visa cards with no forex" (11 Nov 2026): a 4:15 Android voice note → a 60.4 s TikTok with 10 web pages as evidence, Bridge's own architecture diagram, 9 logos, 4 chings. Worked example in `assets/examples/visa-cards/` (script + lay check, cut list, shoot jobs, full `video.json`, post copy, contact sheet).

```
voice note ─► transcribe + islands ─► SCRIPT + LAY CHECK (checkpoint) ─► cut voice (verified edges) ─► tempo + words
                                        │
                                        └► evidence: screenshots w/ target rects · logos · diagrams from docs
                                                                    │
                       video.json timeline (scenes, zooms, stamps, glosses, chings, diagram steps)
                                                                    │
                                  sfx + quiet score + mix ─► stills w/ safe zones ─► render ─► verify
```

## Setup
```bash
SK=~/.claude/skills/evidence-explainer
zsh $SK/scripts/new_explainer.sh "<audio file>" .context/<slug>     # ~1-3 min; prints disk free
cd .context/<slug>                                                  # every script runs from here (W)
```
Needs ffmpeg, Python 3 + numpy + Pillow, Node 20+, Chrome (Playwright drives the installed Chrome), whisper.cpp + `ggml-medium.en.bin` in `~/.cache/whisper.cpp` (`scripts/setup_whisper.sh` builds it; override with `WHISPER_DIR`). The scaffold runs `npm i` in `remotion/`, or clones an existing `node_modules` when `EXPLAINER_NODE_MODULES` points at one (APFS copy-on-write, ~0 bytes). Look = "dev mode" (`src/brand.ts`: dot grid, Space Mono, cyan/yellow/amber); handle/site come from `video.json`.

## The stages (read the reference when you get there)

| # | Stage | Read | Tools |
|---|---|---|---|
| 1 | Script the beats from `sent.txt`, then run the **lay-person check** | `references/01-script-and-lay-check.md` | — |
| 2 | Cut the voice to ≤ 60 s on verified edges, tempo, subtitles | `references/02-voice-cut.md` | `islands_labels.txt`, `dips.py`, `tx.sh`, `cut.py`, `voice.sh`, `words.py` |
| 3 | Evidence: screenshots + target rects, logos, docs diagrams | `references/03-evidence.md` | `shoot.mjs`, `logo_tools.py`, `logo.mjs`, `register_image.py` |
| 4 | Timeline in `remotion/src/video.json` | `references/04-video-json.md` | engine `src/Explainer.tsx` |
| 5 | Sound: clicks, chings, quiet score, mix | `references/05-sound.md` | `sfx_mix.py`, `score.py` |
| 6 | Preview with TikTok safe zones, render, verify | `references/06-render-verify.md` | `remotion/stills.mjs`, `sheet.py`, `verify.sh` |

Quick path once the script is agreed:
```bash
python3 $SK/scripts/cut.py cut.json && zsh $SK/scripts/voice.sh 1.18 "Names, Brands, Jargon"
python3 $SK/scripts/words.py word_fixes.json
node $SK/scripts/shoot.mjs shoot_jobs.json shots && cp shots/*.png remotion/public/shots/ && cp shots/shots.json remotion/src/shots.json
python3 $SK/scripts/logo_tools.py sync                      # after fetching logos
# write remotion/src/video.json, then:
python3 $SK/scripts/sfx_mix.py path/to/music.mp3          # or `none`
(cd remotion && npx tsc -p . && node stills.mjs 45,300,...) && python3 $SK/scripts/sheet.py stills --zones
(cd remotion && npx remotion render src/index.ts Explainer ../out/<slug>.mp4 --codec=h264 --crf=18 --audio-codec=aac --audio-bitrate=192k)
zsh $SK/scripts/verify.sh out/<slug>.mp4
```
A full render of 60 s takes ~40 s; stills ~1 s each after the bundle.

## House style (from the creator's review of the first video — keep it unless told otherwise)
- **Full-screen B-roll.** Screenshots fill the 1080×1920 frame (no browser card); the camera starts wide, then **zooms onto the line that proves the point** while a highlighter sweeps it. A slim `https://domain` pill + yellow `// evidence: …` tag sits top-left.
- **Logos land with a camera click** (white card, slight tilt, scale-down pop, white flash). Show more of them: every company named gets its logo once.
- **"Ka-ching" on every successful transaction** (account created, money received, wallet topped up, payment approved) with a green ✓ chip and ring.
- **Architecture for lay people.** One diagram (You → App → Infrastructure → Card), with logos in the nodes, built up step by step ("STEP 1 · SIGN UP"…), with labelled packets travelling between nodes. A provider's own developer diagram is shown only **zoomed into its plain-English boxes**, never whole.
- **Ask yourself after writing the script: will this clarify or confuse a lay person who uses the product?** Fix every "confuse" before building (gloss cards, simpler labels, no code styling). Put the check in the script file and in the summary.
- **Subtitles anchored to the bottom**: the box's bottom edge is fixed 400 px above the frame bottom (just over TikTok's username/caption block), 2-line pages grow upward, padded off the right action rail.
- **Hook first** (big dot-matrix word + the viewer's question over the first evidence, blurred), **follow CTA last** (logo chain recap, FOLLOW, handle, button, site).
- Music is a quiet bed (score.py BASE −26 LUFS): a loud dramatic score tested as "way too high and annoying".

## Checkpoints (stop and ask, with a recommendation)
1. **Script + lay check** before cutting anything: the beat table (what he says → what's on screen) and the confuse/clarify table.
2. **Claims you can't verify** (e.g. "app X uses provider Y"): keep them in his words, word the on-screen labels as "e.g." / "one example", and flag them.
3. **Before rendering**: stills of every new element with `--zones`.
4. **Before publishing**: logo licences (CC BY/BY-SA need a credit line), hedged claims ("most likely" stays visible), names Whisper misheard (captions use the right spelling even if he said it oddly). Upload only when asked.

## Working principles
- **Evidence over assertion**: every factual beat gets a page that says it, captured live, zoomed to the line. Prefer primary sources (company newsroom, official docs, the regulator/central bank, the app's store page) over blogs. Note what a page does NOT say (Bridge's country table = who can be onboarded, not card availability) and label accordingly.
- **Cut on verified edges only**: energy islands + bisected dips (`tx.sh`), never Whisper word times (they drift up to seconds on phone audio). Re-transcribe the final cut and the render.
- **Glosses are short and concrete**: "stablecoin = a digital dollar, 1 USDC ≈ $1", "KYC = the ID + selfie check you did when signing up", "API = a plug that lets apps use X".
- **Zoom limits**: a 1200 px mobile screenshot fills the frame at zoom 1.0 (it is already cropped ~36 px a side); paragraphs tolerate ≤ 1.3, short targets (a code line, a table row) 1.8–2.0. Check that the highlighted words and any key column (e.g. currency) stay inside the frame.
- **Verify, then report**: durations (video vs audio), −14 LUFS / peak ≤ −1, full transcript of the render, chings ≥ +5 dB over the voice, a contact sheet you looked at. Say what you chose by tag without listening (music).

## Final summary format
Deliverable path + length; a contact sheet image; what's on screen, beat by beat (short); the lay-person check verdict; "check before posting" (unverified claims, licences, hedges, misheard names); housekeeping (working dir, disk, re-render cost, which file to edit).
Files in this package (4)
  • .gitignore 1 KB
  • LICENSE 1 KB
  • README.md 6 KB
  • SKILL.md 8 KB

Versions

The database has no other skills named evidence-explainer.

Database snapshot: 13.11.2026 · package version 5ab9cd8df076 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100make-screen-videos
    Turn a screen recording of an app or website into finished videos - several standalone how-to shorts for Reels, TikTok or Shorts that each teach one easy thing, a feature explainer, a promo with each request typed over its result, a timelapse of a long session, or a step-by-step…
  • 100make-screen-videos
    Turn a screen recording of an app or site into videos - standalone how-to shorts for Reels, TikTok or Shorts each teaching one easy thing, a feature explainer, a promo with each request typed over its result, a long session's timelapse, or a step-by-step 16:9 tutorial with…
  • 100video-to-shorts-skill
    Video to shorts skill: turn a long video (podcast, interview, talk, webinar, stream, YouTube video) into vertical short clips for TikTok, Instagram Reels and YouTube Shorts, then post them to one or many accounts with WoopSocial. Transcribes with word timestamps (free local…
  • 100clip
    Turn a long video, podcast, stream or interview into vertical Shorts, Reels or TikToks with word-by-word captions, an on-screen hook, and a ready-to-post title, description and hashtags. Use when someone wants clips, shorts, reels, highlights or "the best moments" cut from a…
  • 100short
    Make a short vertical (9:16) lpm lesson that feels native to TikTok, Reels and Shorts: a payoff-first hook, fast push-ins that follow the action, word-by-word burned-in captions, numbered step stickers, jump cuts over waiting, recorded from the real desktop app. Topic in,…
  • 100instagram-reels
    Direct, storyboard, animate and render premium vertical Instagram Reels, Shorts and TikToks from a topic, script, footage or voice audio. Use when users request social videos, visual hooks, smooth motion design, word-timed captions, explainer graphics or a finished code-rendered MP4.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.