recording-demo-videos
Skill731 starsChanged 4 days agoMITView on GitHub
Records a captioned, PostHog-branded walkthrough video (MP4) of a feature running on the local PostHog stack, for a Loom, a Slack demo, or a PR. Use when asked to record a video, demo, walkthrough, or Loom of a change end to end, including flows that leave the app, such as an API call shown as a terminal card or an email arriving in the local inbox. The recorder drives the real app, zooms in on the beats the storyboard marks, adds RoundHog captions, a pointer, hedgehog stickers, and an optional ElevenLabs voiceover and music bed, and frames the video with title and end cards that carry the logo and a hedgehog from @posthog/brand. For a short animated WebP of one interaction in a PR description, use the reel mode of qa-frontend.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- PostHog/posthogword for word, first seen Oct 20, 2026
- vribeirocmp/recording-demo-videostheir own version, first seen Oct 17, 2026
Other versions2 projects use a version of this.
Word for word · 1
- PostHog/posthog★ 41k100% same
Edited · 0
None found.
Wrote their own version · 1
- vribeirocmp/recording-demo-videos★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository127 other files it gives its agents.
- AGENTS.mdAGENTS.md
- common/AGENTS.mdAGENTS.md
- hog/AGENTS.mdAGENTS.md
- proto/AGENTS.mdAGENTS.md
- rust/AGENTS.mdAGENTS.md
- .cursor/rules/django-python.mdcCursor rule
- .cursor/rules/react-typescript.mdcCursor rule
- .cursor/rules/rust.mdcCursor rule
- adding-activity-loggingSkill
- adding-api-scopesSkill
- adding-inbound-webhooksSkill
- adding-inbox-sourcesSkill
- adding-ingestion-warningsSkill
- adding-mcp-store-serversSkill
- adding-personhog-rpcSkill
- adding-product-alertingSkill
- adding-project-secret-api-key-authSkill
- adding-today-highlightsSkill
- adopting-generated-api-typesSkill
- analyzing-experiment-precompute-canarySkill
- analyzing-experiment-query-performanceSkill
- analyzing-insights-across-teamsSkill
- announcing-behavior-changesSkill
- auditing-llm-gateway-paritySkill
- auditing-warehouse-source-coverageSkill
- authenticating-to-clickhouseSkill
- authoring-ci-workflowsSkill
- building-product-empty-statesSkill
- building-the-toolbarSkill
- clickhouse-migrationsSkill
- creating-customer-analytics-account-widgetsSkill
- debugging-ci-failuresSkill
- debugging-local-replaySkill
- debugging-local-task-agent-runsSkill
- debugging-mcp-analyticsSkill
- debugging-signals-pipelineSkill
- debugging-table-access-deniedSkill
- depot-ciSkill
- depot-container-buildsSkill
- depot-github-runnersSkill
- developing-subscriptionsSkill
- developing-the-cliSkill
- django-migrationsSkill
- django-startup-timeSkill
- documenting-warehouse-sourcesSkill
- editing-agents-mdSkill
- establishing-code-ownershipSkill
- extending-hobby-smoke-testsSkill
- extending-personhog-test-harnessSkill
- extending-the-admin-consoleSkill
- finding-llm-gateway-migration-candidatesSkill
- fixing-flaky-testsSkill
- formatting-slack-messagesSkill
- gating-production-deploysSkill
- gating-sensitive-actionsSkill
- generating-clickhouse-query-performance-reportsSkill
- hogliSkill
- implementing-mcp-toolsSkill
- implementing-mcp-ui-appsSkill
- implementing-warehouse-sourcesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Use qa-frontend instead for a reel: a short animated WebP of one interaction, made from stills, for a PR description.
- Very specific: line 34
Start it with hogli start -y -d and hogli wait, or follow /run-posthog.
- Distinctive: line 35
Check the processes the flow needs beyond the web app.
- Very specific: line 49
Use reserved domains (example.com) or a domain you control for addresses, and invented names.
- Distinctive: line 53
Write three small scripts for the demo: seed the starting state, reset it before every take, and check that the flow works once before the …
- Distinctive: line 60
Read references/storyboard.md for the format and a full example.
- Distinctive: line 65
Start in the state just before the new behavior.
- Distinctive: line 71
Write them to be read aloud too, when the video has a voiceover.
- Distinctive: line 80
Keep captions under ten words.
- Very specific: line 81
Leave hold unset. The defaults hold a caption for about a quarter of a second per word, at least one and a half seconds.
- Very specific: line 101
When a step fails, it writes <output>.error.png and exits non-zero.
- Distinctive: line 105
Read the contact sheet before you share anything.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Recording demo videos
A demo video shows a feature working, from the first click to the proof that it worked. The recorder drives the real app on the local stack, so what the viewer sees is what the code does. It writes a short MP4, usually under a minute, a contact sheet of frames to review, and a log.
The output looks like this: a title card with the logo and a hedgehog, the app with a caption bar and a pointer that glides to each click, terminal cards for API calls, and an end card. Page loads stay out of the video, so it moves at reading speed. A step can also zoom in on the button it clicks or on the detail it proves. A voiceover can read the captions, a music bed can sit under it, and a step can pop in a hedgehog sticker with a short sound.
Use qa-frontend instead for a reel: a short animated WebP of one interaction, made from stills, for a PR description.
For a narrated or musical promo video, see hogreel.
For a raw take with no captions or narration, frame-perfect at 60 fps, PostHog staff can use recording-web-demos from the team skills store (skill-get in the PostHog MCP). It steps the page clock frame by frame, so it never judders.
Workflow
1. Get the stack ready
The stack must be up and serving the code you want to show.
Start it with hogli start -y -d and hogli wait, or follow /run-posthog.
Check the processes the flow needs beyond the web app.
For example, workflow runs and email sends need the CDP workflow workers, which the default dev stack does not start.
references/troubleshooting.md lists the ones that caught us.
The recorder needs ffmpeg and the repo's Python environment, which has Playwright.
It reads the brand assets from frontend/node_modules/@posthog/brand, so run pnpm install first if that directory is missing.
2. Seed the data the demo needs
Record in a local demo workspace, never in a workspace with real data, because the video can end up in a public PR.
python manage.py setup_dev --no-data creates one with the test@posthog.com user.
Seed everything else the flow needs with a short script: feature flags, objects to start from, API keys.
Invent all the data.
Use reserved domains (example.com) or a domain you control for addresses, and invented names.
Some flows validate a domain, for example the email sender refuses a domain without mail servers, so check what the flow accepts.
Each take changes state: it creates objects, sends emails, and bumps versions. Write three small scripts for the demo: seed the starting state, reset it before every take, and check that the flow works once before the first take. references/seeding.md shows how to work out what the flow needs and how to write each script.
3. Write the storyboard
A storyboard is a JSON file: optional title and end cards, then a list of steps. Each step can navigate, click, type, wait, show a caption, or show an HTTP request as a terminal card and send it. Read references/storyboard.md for the format and a full example.
Plan the beats before you write steps:
- The title card says what the feature does for the viewer, in one line.
- Start in the state just before the new behavior. Skip the navigation a viewer already knows.
- One step per action, with a caption that says what is happening and why it matters.
- Show proof of the effect: the email in the inbox, the row in the table, the number in the chart.
- The end card sums up the change in one line.
Captions are user-facing copy, so /writing-user-facing-copy applies: sentence case, one idea each, no em dashes.
Write them to be read aloud too, when the video has a voiceover.
Pacing
A demo that drags loses the viewer. Keep it short, and keep it moving.
- Aim for 30 to 60 seconds. Go past 90 seconds only when the flow needs every beat. Cut beats before you add time.
- Change something on screen at least every two seconds. A still frame is a pause, even with a caption on it.
- Show each idea once. Cut a step that proves nothing new.
- Keep captions under ten words. A long caption holds its step longer, and a long voiceover line holds it longer still.
- Leave
holdunset. The defaults hold a caption for about a quarter of a second per word, at least one and a half seconds. With a voiceover, a step waits for its line to finish. - Set
holdonly to give a sticker time to land or to make a navigation step shorter. Keep it at two seconds or less. - Zoom on the two to five beats that matter: the key click, and the detail that proves it worked. A zoom on every step makes the video seasick.
For a voiceover or music, add voiceover or music to the storyboard.
They need an ElevenLabs API key in ELEVENLABS_API_KEY. Do not ask the developer to paste the key into the chat.
Without the key, the recorder leaves out the voiceover and generated music and records a captioned video.
The log lists what it left out under skipped_without_elevenlabs_key. Tell the developer, and point them to references/troubleshooting.md to set the key.
Settle the captions in a silent take first, because every changed line costs credits.
4. Record
From the root of the checkout:
uv run python .agents/skills/recording-demo-videos/scripts/record_demo.py path/to/storyboard.jsonThe script logs in, loads every page once to warm the dev server, then records.
It writes <output>.mp4, <output>.sheet.png and <output>.log.json next to the storyboard.
When a step fails, it writes <output>.error.png and exits non-zero. The log names the step.
5. Review, then record again
Read the contact sheet before you share anything. Most first takes need another one. Look for:
- pauses: frames where nothing changes for more than two seconds, or a
durationin the log over 60 seconds. Remove thehold, shorten the caption, or cut the step. - spinners, skeletons or empty tables where the step expected data. Add a
wait_foron the content. - numbers that disagree with what happened in the video.
- debug chrome, banners and toasts that distract. Add them to
hide_textorhide_selectors. - with a voiceover: the
voicelist in the log, which gives each line's start and length in the video. A line that runs long holds its step, so a step that lingers often has a long line. Trim the line. - secrets, real names, or anything else that must not be public, in the pixels and in the captions.
Reset the data, then record again. Read individual frames with ffmpeg when the sheet is too small to judge.
6. Share
In a PostHog Desktop or cloud task, upload the MP4 as a task artifact.
For a PR, run hogli pr:upload-video. With an open PR it attaches the video to the description as an inline player. Without one it prints a link to paste.
PR assets are public forever, so check the frames for private data before every upload.
References
- references/seeding.md: working out what a flow needs, and the seed, reset and check scripts.
- references/storyboard.md: the storyboard format, targets, variables and secrets, voiceover, music, and a full example.
- references/branding.md: where the brand assets come from, the rules for the logo, colors, type and hedgehogs, and hogreel.
- references/troubleshooting.md: failures we hit while recording, and their fixes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

