Skip to content
Back to search

video-demo

SkillWorks with Claude CodeGitHub

Films a web app as narrated, zooming, cursor-driven demo videos with retina screenshots, either from a repo it builds and mocks or from a live URL as it is served. Use when the user asks for a demo video, product video, walkthrough, screencast, screen recording of an app or of a URL, hero or landing-page footage, app screenshots for a website, "show off this feature", "record a demo of <url>", or wants to add, re-film, re-narrate or fix a demo scene.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nilbuild--video-demo/badge.svg)](/listings/nilbuild--video-demo)

HTML

<a href="/listings/nilbuild--video-demo"><img src="/api/listings/nilbuild--video-demo/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 141 lines
  1. ---
  2. name: video-demo
  3. description: Films a web app as narrated, zooming, cursor-driven demo videos with retina screenshots, either from a repo it builds and mocks or from a live URL as it is served. Use when the user asks for a demo video, product video, walkthrough, screencast, screen recording of an app or of a URL, hero or landing-page footage, app screenshots for a website, "show off this feature", "record a demo of <url>", or wants to add, re-film, re-narrate or fix a demo scene.
  4. ---
  5. # Video demo
  6. `scripts/demo` films a web app and writes `demo-out/` into that project's
  7. workspace: per scene an mp4 with voice-over, a poster, retina stills, plus
  8. `full-tour.mp4`, `manifest.json` and `index.html`. All local. The engine runs
  9. from this skill; nothing is installed into the app being filmed.
  10. ## Non-negotiables
  11. Each of these cost a run or a user's patience.
  12. 1. **A pinned build, never a dev server.** Its module graph belongs to whoever
  13. is editing source. Copy it somewhere private and verify its API base by
  14. reading the bundle. A URL with no repo behind it is `site` mode; a URL on
  15. localhost is a dev server and is never filmed.
  16. 2. **In `build` mode, mock every request in-process and pin the clock.** A
  17. corpus gets published, and a real account publishes real people's
  18. addresses. `site` mode trades both away knowingly: public pages only.
  19. 3. **Own your port and output directory.** The studio refuses to adopt a server
  20. it did not start. Never `pkill` by pattern.
  21. 4. **1080p60 video, 2x stills.** They are separate settings. 4K video judders
  22. because throughput is a fixed pixels-per-second budget.
  23. 5. **Do the gesture, then narrate while pushed in on the result.** One subject
  24. per line. Never narrate before the subject exists. Where the app has its own
  25. timer — an undo window, a toast — the gesture goes inside it and the words
  26. after, or the film shows a feature that does not work.
  27. 6. **One scene, then stop and ask** (step 8). It caught four defects before
  28. twenty-six more scenes were filmed.
  29. 7. **Read the PNG, every time.** A scene that passes while framing the wrong
  30. thing is a failure, and only an eye on the still catches it.
  31. 8. **Nothing is final until they say so.** Any note about the words, the
  32. framing, the pace, what is covered or the voice is a re-film, not a
  33. negotiation: change it and film it again. They cannot see what you can, so
  34. "too long", "zoom in more" and "stop zooming so much" are all complete
  35. instructions, and a scene is cheap to shoot twice.
  36. ## Workflow
  37. 1. **Pick the mode from what you were given. Do not ask.** An http(s) URL on
  38. a public host is `site`, workspace `~/.video-demo/<host>/`. A URL on
  39. localhost or a private address is a dev server: find the repo behind it and
  40. treat the request as that repo. No URL means the repo you are in, so walk
  41. up and look for a web app (a `package.json` with a build script beside a
  42. Vite, React Router, Next, Astro, SvelteKit or Remix config). Exactly one is
  43. `build`; several, ask which; none, ask for a URL or a path. A workspace
  44. whose `.origin` already names this repo is reused, not scaffolded again.
  45. Say the mode and the workspace path in one line and carry on.
  46. 2. `scripts/doctor.sh`, then **set yourself up before asking anything else of
  47. the user.** They installed a skill; they did not sign up to run three
  48. scripts. Say what is missing in one line, say what you propose to install
  49. and roughly how big it is, and run it once they agree. `scripts/install.sh`
  50. covers the engine and Chromium (about 250MB) and installs ffmpeg too where
  51. a package manager allows it; `scripts/install-voice.sh` is the voice
  52. (~350MB), and filming silent is a fine answer if they would rather not.
  53. Never install anything without asking, and never hand them a doctor report
  54. to interpret. Two things it will not do, and nor should you: upgrade their
  55. Node, because which tool owns it is theirs to know, and run `sudo`, because
  56. a password prompt in a script nobody is watching just hangs. In both cases
  57. the script prints the one command and you pass it on.
  58. 3. **Discover, writing nothing.** `site`: open the URL and read it, for what
  59. the page is for, the three things worth showing, and what is stable enough
  60. to point at. If it lands on a sign-in, stop: a signed-in app is filmed from
  61. its repo, so ask for that or for a public URL. `build`: the build command
  62. copied verbatim out of `package.json`; the output directory from the
  63. framework's config; any absolute API host in `.env*` (it goes in
  64. `build.forbid`); the key the theme boot script reads; an existing fixture
  65. API or MSW handlers; `data-testid` density; routes with no credential.
  66. 4. `scripts/scaffold.mjs <appRoot>`, or `scripts/scaffold.mjs --site <url>`.
  67. Neither writes anything into the app.
  68. 5. **Fill in the workspace's `demo.config.ts`.** A required field still
  69. unknown means discovery is not done. [config.md](references/config.md)
  70. 6. **`build` only: write `mock.ts` and `seed/`.** Reuse the repo's own data
  71. fixtures where it has them, but never a file that imports
  72. `@playwright/test`: two copies in one run is an error Playwright refuses,
  73. and it fails the whole corpus rather than the one scene that did it. Then
  74. `DEMO_VOICE=0 scripts/demo --grep smoke`. Reuse the repo's fixture API if it has one
  75. ([mocking.md](references/mocking.md)). Read the still: signed in, seeded
  76. data, right theme, no login page. Read the capture line. Fix until both are
  77. right, then write `demo/ui.ts` with only what the smoke run proved.
  78. 7. **Film what they asked for, at the scope they asked for it.** A named
  79. feature is one scene: write it, film it, hand it over. Do not answer "record
  80. the search on the home page" with a ten-scene proposal, and do not quietly
  81. widen the ask because the product has more in it. Only when the request is
  82. the whole product do you **propose 6 to 10 scenes**, each a title and a
  83. one-line blurb in tour order, and ask which to film first.
  84. 8. **STOP.** Film that one scene with voice. Verify the spoken count matches the
  85. `say` calls, nothing overran, the rate held. Read every still. Give the user
  86. the mp4 path and ask about the writing's register, the zoom scale, the pacing
  87. and the voice. **Write nothing else until they answer.**
  88. 9. Then batches of three or four via `--grep`; the manifest merges. Read the
  89. stills after every batch. `DEMO_BUILD=0 scripts/demo` skips the rebuild while iterating
  90. on a scene — twenty seconds instead of four minutes; drop it for the run
  91. that produces the corpus.
  92. 10. Full run with `DEMO_TRACE_FRAMES=1`, then `scripts/gaps.mjs` and open
  93. `demo-out/index.html`. Report the capture table and any slow clips.
  94. ## A scene
  95. ```ts
  96. scene('tasks', { title: 'Your to-dos, beside your calendar', blurb: '...' },
  97. async ({ actor, page, shot }) => {
  98. await actor.click(page.getByRole('radio', { name: 'Today' }));
  99. await actor.settle();
  100. await actor.spotlight(
  101. row('Send Sam the feedback'),
  102. 'And this one is from yesterday that I never got to, so it is flagged.',
  103. { scale: 1.8, stay: true }
  104. );
  105. await shot('overdue');
  106. await actor.unfocus();
  107. });
  108. ```
  109. `spotlight` takes the narration mark, then moves camera and cursor over the
  110. line's opening words. Scale by subject: panel ~1.4, row ~1.7, single control ~2.
  111. A line about the whole screen gets a plain `say` and no zoom. `unfocus` is a
  112. hint rather than a movement: the camera only comes out when something needs
  113. it wide, so consecutive beats about the same region glide instead of bouncing.
  114. [scenes.md](references/scenes.md) · [narration.md](references/narration.md)
  115. ## Never
  116. Subtitles (the voice is the channel). Cloud TTS (the film is of private data).
  117. Playwright's `recordVideo` (no control of rate, size or start; the recorder
  118. replaces it). 4K as a default. Music, intro cards or cross-fades. Scenes
  119. generated from a route crawl: a scene is choreography with a point. Retries: a
  120. retried scene is a different film.
  121. ## Also
  122. [capture.md](references/capture.md) before changing any capture number.
  123. [runs.md](references/runs.md) for builds, isolation and the manifest.
  124. [troubleshooting.md](references/troubleshooting.md) when a run dies or a shot
  125. looks wrong. The engine runs from this skill, so a fix to `engine/` reaches
  126. every project on the machine at once: edit it there, and nothing needs
  127. propagating.
README.md · README · 51 lines
  1. <img src=".github/video.svg" width="130" alt="">
  2. # /video-demo
  3. Skill to make your agent record demo of your web app with voice over all on your machine.
  4. Given below is a sample video generated using the skill for [roadmap.sh](https://roadmap.sh).
  5. https://github.com/user-attachments/assets/c20907c2-89a4-42a8-95d6-271ba3a60b80
  6. ## Record a Demo
  7. Install the skill
  8. ```bash
  9. npx skills add nilbuild/video-demo
  10. ```
  11. Then ask your agent
  12. ```bash
  13. /video-demo [explain what to recorded]
  14. /video-demo record a demo of https://example.com
  15. /video-demo record the checkout flow on https://example.com, use cash on delivery
  16. /video-demo visit http://roadmap.sh and record the roadmap search flow
  17. /video-demo record the login flow in the current project
  18. ```
  19. Be as broad or as specific as you like. You can also add video instructions too e.g. "tell them it works offline now", "mention the keyboard shortcut", "keep it under twenty seconds".
  20. ## Ask for updates
  21. If you are not happy with the produced recording, you can ask for updates to the recorded video e.g.
  22. - "that line is too long", "say screenshots, not stills"
  23. - "zoom in more on the toolbar", "stop zooming so much"
  24. - "slow down at the end", "say thanks for watching at the end"
  25. - "record the calendar first", "record the pricing page too"
  26. - "try a different voice", "no voice-over on this one"
  27. Say what is wrong and it can keep re-recording until you are happy.
  28. ## What you get
  29. An mp4 video is produced with the voice-over on it. It also keeps screenshots at every moment
  30. worth keeping. Everything is done on your local machine.
  31. ## Licence
  32. MIT © [Kamran Ahmed](https://kamran.fyi).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.