diorama: Skill for Claude Code

.claude/skills/record-extension-demo/SKILL.md

record-extension-demo is a skill for Claude Code from daniel-ddtech/diorama. It costs 47 tokens per session (888 once invoked), scanned A, original, MIT.

A workflow for recording polished demo videos of Chrome extensions with Diorama. It uses a YAML beat sheet, a written sequence of actions, to control a real unpacked Manifest V3 extension in Chrome.

In plain words
What is it for?
Use it to create or update Chrome Web Store demo videos, re-record an extension demo, or present an extension feature. It requires Chrome for Testing or Playwright Chromium and ffmpeg.
Why use it?
It helps produce repeatable extension demos without screen recording or operating-system permissions, while adding a browser frame, cursor, click effects, and camera movements.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is daniel-ddtech/diorama's own configuration. It tells Claude Code how to work on diorama itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything diorama configures →

Reuse

Borrowing it

Nothing to install: this file belongs to daniel-ddtech/diorama. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/daniel-ddtech/diorama/main/.claude/skills/record-extension-demo/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/daniel-ddtech/diorama

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for record-extension-demo

README.md
[![agentmods](https://agentmods.dev/badge/skills/daniel-ddtech/diorama/record-extension-demo.svg)](https://agentmods.dev/skills/daniel-ddtech/diorama/record-extension-demo)
Your own site
<a href="https://agentmods.dev/skills/daniel-ddtech/diorama/record-extension-demo"><img src="https://agentmods.dev/badge/skills/daniel-ddtech/diorama/record-extension-demo.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 888 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00888
Opus 5 $0.00023 $0.00444
Sonnet 5 $0.00009 $0.00178
Haiku 4.5 $0.00005 $0.00089

Measured 7d ago against content hash 18415da46b87, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

record-extension-demo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/record-extension-demo/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Record an extension demo with Diorama

Diorama records real Chrome extensions headlessly from a YAML beat sheet and composites a finished mp4 with a drawn browser frame, synthetic cursor, click ripples, and camera moves. No screen recording, no OS permissions.

Workflow

  1. Check the environment: diorama doctor (or node <diorama>/packages/cli/dist/main.js doctor). Needs Chrome for Testing (DIORAMA_CHROME or a Playwright Chromium) and ffmpeg.
  2. Find the extension's unpacked directory (contains manifest.json, must be Manifest v3). Read the manifest to learn the popup path and the extension name.
  3. Write a beat sheet. Start from diorama init or this shape:
version: 1
title: My extension demo
viewport: { width: 1280, height: 860, scale: 2 }   # +100px toolbar = 4:3
extension:
  path: /abs/path/to/extension
  popup: { width: 600, height: 600, autoSize: true }
steps:
  - verb: goto
    url: https://the-page-the-extension-works-on.example
  - verb: wait
    selector: "css-or-text=selector"
  - verb: openPopup
  - verb: camera
    zoom: 1.35
    focus: popup
    ms: 700
  - verb: click
    target: popup
    selector: text=The Button Label
  - verb: wait
    target: popup
    expression: /done|complete/i.test(document.body.innerText)
  - verb: hold
    ms: 1200
  - verb: mark
    name: end

Verbs: goto, wait (selector | ms | expression), click, type, scroll, hover, openPopup, closePopup, camera (zoom 1-2.5, focus page|popup, ms), hold, mark. text= selectors match visible text case-insensitively. The last mark is the poster frame. Optional blocks: frame (theme dark|light|custom html path, url, title), profile (dir, seedStorage), cursor (scale, ripple, shadow), output (fps, endCard true|false|{title,subtitle}, posterAt, formats list).

  1. Record: diorama record demo.beats.yaml --out out/ --keep-run.
  2. Inspect the result before declaring success: extract frames with ffmpeg (ffmpeg -ss <t> -i out/<title>.mp4 -frames:v 1 check.jpg) and view them. Common fixes: add wait steps before clicks that miss, add holds so states breathe, adjust camera timing to land after UI settles.
  3. Iterate by editing the sheet and re-running. Recordings are reproducible.

Read the full file on GitHub · 82 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 82 lines · 47 tokens per session scan A 18415da46b87

Subscribe to this mod's changes

record-extension-demo is a skill published in the GitHub repository daniel-ddtech/diorama (0 stars, last pushed 21d ago), licensed MIT. It adds 47 tokens to every session and 888 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

demo

Record a short demo VIDEO of a PR or feature — drive the repo's web UI in a real headless browser, capture the session, and composite a titled, size-capped mp4 with ffmpeg. Use on the docker QA image when the deliverable is a playable demo clip (single walkthrough or before/after comparison), not a text/screenshot…

nearform/lastlight · 75 tokens

demo-video

Produce a polished, ScreenStudio-style 60fps product demo video of a web app with a tiny, dependency-light pipeline — Playwright frame capture + a multiprocess Pillow compositor streaming into ffmpeg (no Node/Remotion). Drives the app one step per frame so playback is true 60fps regardless of capture speed, then…

surajshetty3416/demo-video-skill · 181 tokens

demo-video

A process for automatically recording feature-demo videos of a local web app using Playwright, a browser-automation tool, and ffmpeg, a video-processing tool. It drives the real app, then adds subtitles, labels, a simulated cursor, zooms, and faster playback for waiting periods.

Kminer2053/demo-video-skill · 261 tokens

annotation-feedback-wait

A workflow for collecting and waiting for visual feedback that users draw on a web page with a browser annotation tool.

cc10143/annotation-overlay-mcp · 90 tokens

annotation-browser-launch

A workflow for opening an agent-controlled browser with a page-annotation extension so a user can mark up a web page.

cc10143/annotation-overlay-mcp · 86 tokens

cleya-edit-craft

The grammar of cuts — which cut to use, when to cut, and how to pace an ad. Read before authoring any multi-shot film.

severment/cleya · 36 tokens