demo
Skill0 starsChanged 10 days agoMITView on GitHub
Record a finished feature in the developer's locally running app, one scene per acceptance criterion, and post the video or screenshots with a chapter list as one Redmine comment after approval. Use when the user asks to demo a ticket, record a walkthrough for PM or QA, or replace a demo meeting with a video on the ticket.
- Installs packages
26 other projects use a version of this.
Adopted by
Most recently taken up by
- yarikleto/claude-teacher-plugintheir own version, first seen Nov 14, 2026
- NahumLitvin/prismantistheir own version, first seen Nov 13, 2026
- nivoset/skillstheir own version, first seen Nov 12, 2026
- eliasstravik/skillstheir own version, first seen Nov 11, 2026
- serhiileniv/skillstheir own version, first seen Nov 8, 2026
- serhiileniv/ccstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use spec, implement and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 4 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 4 projects that use this
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- NahumLitvin/prismantis★ 426same name
- iamrohithrnair/merman★ 42same name
- eliasstravik/skills★ 22same name
- yarikleto/claude-teacher-plugin★ 15same name
- calebnewtonusc/Chewbacca★ 8same name
- malinskibeniamin/skills★ 4same name
- nivoset/skills★ 4same name
- pcode-xyz/simple-skills★ 4same name
- developzone5/sanad★ 3same name
- raphaelDkhn/worldbuilder★ 3same name
16 more not listed
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 repository6 other files it gives its agents.
- calibrateSkill
- estimateSkill
- logSkill
- postmortemSkill
- spec-interviewSkill
- sprint-planSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Ask for the app's local URL, and for Redmine's maximum attachment size (Administration, Settings, Files.
- Very specific: line 58
Run node "$S/session.mjs" signin "$STATE" <url> in the background.
- Very specific: line 60
Ask with AskUserQuestion whether they are signed in.
- Very specific: line 69
Read the ticket and its spec the way /estimate step 1 does: rmine issue view <id> --comments -o json, then the Google Doc, attachment or …
- Very specific: line 78
Read references/scene-script.md before writing $OUT/scenes.json: the format, and what makes a take worth the watchers' time.
- Very specific: line 109
Run git status --porcelain --untracked-files=no.
- Very specific: line 130
Read sheet.png first. Each frame should show its scene's criterion plainly, with the caption clear of what it describes.
- Distinctive: line 148
Ask with AskUserQuestion: after the developer has seen the video and the comment.
- Distinctive: line 157
If they decline, tell them where the files are.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Demo
A finished feature waits for a demo meeting before QA gets it. This skill replaces the meeting: drive the developer's local app through the ticket's acceptance criteria, film one take, and post it with a chapter list so PM and QA can reply against a time ("at 1:30 the empty state is wrong").
The take is real footage of the real app, and every scene ends on a check. A failed check stops the run and deletes the video, so a demo only ever shows a feature that works.
The skill works through the browser alone. Servers, data and sign-in belong to the developer: they start the app, create any data a scene needs, and type their own password. The only write to Redmine is one comment, posted after an explicit yes (step 6).
$S is ${CLAUDE_PLUGIN_ROOT}/skills/demo/scripts. Run from inside the
product repo.
0. Preflight
rmine whoami && rmine version && node -v && ffmpeg -version | head -1rmine v0.7.0 or later (if missing: go install
github.com/mehboobali98/rmine/cmd/rmine@latest, then rmine config init),
Node 18 or later, ffmpeg and ffprobe. If
${CLAUDE_PLUGIN_ROOT}/node_modules/playwright is missing, install it:
npm install --prefix "${CLAUDE_PLUGIN_ROOT}"
npx --prefix "${CLAUDE_PLUGIN_ROOT}" playwright install chromiumSettings, the session and all output live per user and per repo, outside the repo:
REPO=$(basename "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")
STATE="${XDG_STATE_HOME:-$HOME/.local/state}/rmine-skills/demo/$REPO"
OUT="$STATE/<id>"
node "$S/session.mjs" check "$STATE"Exit 0: go to step 2. Exit 4: step 1. Exit 3: the app isn't reachable at the printed URL; ask the developer to start it, and stop.
1. Sign in (once per machine and app)
- Ask for the app's local URL, and for Redmine's maximum attachment size (Administration, Settings, Files; 5 MB if they don't know).
- Run
node "$S/session.mjs" signin "$STATE" <url>in the background. A browser window opens; the developer signs in there. - Ask with AskUserQuestion whether they are signed in. On yes,
touch "$STATE/.signed-in". - Set
max_attachment_mbin$STATE/settings.json.
Done when session.mjs check exits 0. (Exit 4 from signin: a password field
is still showing. Exit 6: the window closed or 15 minutes passed.)
2. Script the scenes
Read the ticket and its spec the way /estimate step 1 does:
rmine issue view <id> --comments -o json, then the Google Doc, attachment or
description, and linked issues.
Draft one scene per acceptance criterion, each with a caption and a check that proves it. With no acceptance criteria, draft from the description and say so. Propose video when any scene has a flow worth watching, screenshots when every scene ends in one static state.
Read references/scene-script.md before writing $OUT/scenes.json: the
format, and what makes a take worth the watchers' time.
Done when the developer has approved the scene list, in order and with each
scene's reason for its place, and the format with AskUserQuestion, and any
criterion that can't be filmed is in omitted with its reason.
3. Rehearse, then record
Rehearse unrecorded until every scene passes. Each run prints PASS, FAIL or
STOPPED per scene and leaves look.png and look.aria.txt (the page's
accessibility tree) from where it stopped; read both to find the next locator.
--scene N --steps K stops partway through a scene, after running the scenes
it carries on from.
node "$S/run.mjs" rehearse "$OUT/scenes.json" "$STATE" "$OUT" [--scene N --steps K]
node "$S/run.mjs" record "$OUT/scenes.json" "$STATE" "$OUT" # or: screenshots| Exit | Do |
| 0 | Step 4 |
| 1 | Read failure.png and failure.aria.txt. A wrong locator or timing is a script fix: fix, rehearse, record again. A feature that misbehaves is a finding: stop, and tell the developer which scene and what was on screen. Checks stay as strict as the criterion |
| 2 | Fix the script errors it lists |
| 4 | The app showed a sign-in page: step 1, then record again |
Done when record (or screenshots) exits 0.
4. Assemble
Run git status --porcelain --untracked-files=no. If it lists files, show
them to the developer: pass --dirty unless every one is generated output
that doesn't change what was filmed (compiled CSS a dev server rewrites).
node "$S/assemble.mjs" "$OUT" --subject "<ticket subject>" \
--branch "$(git rev-parse --abbrev-ref HEAD)" --sha "$(git rev-parse --short HEAD)" \
--limit-mb <max_attachment_mb> [--dirty] [--parts 2]It cuts page loads out of the take, encodes demo.mp4 with chapter markers to
fit the limit, and writes sheet.png (each scene's final frame),
demo-chapters.json and comment.md. It prints comment: and one attach:
line per file.
Exit 5: the video can't fit the limit and stay readable. Ask the developer
with AskUserQuestion: screenshots instead, or --parts 2 for two videos on
the comment.
5. Review
Read sheet.png first. Each frame should show its scene's criterion plainly,
with the caption clear of what it describes; re-script any scene whose frame
doesn't. Then open "$OUT/demo.mp4" for the developer and show sheet.png
and the exact text of comment.md.
Done when the developer has seen all three.
6. Post, after an explicit yes
rmine issue comment <id> --file "$OUT/comment.md" --attach "$OUT/demo.mp4"Repeat --attach for each attach: line. Post the file that was shown: text
passed inline gets rewritten by the shell.
The approval rules are /spec-interview step 6's:
- Ask with AskUserQuestion after the developer has seen the video and the comment. Only a chosen yes counts.
- The yes covers this comment and these files. "Demo 123 and post it" authorises the run; the comment it produced still needs its own yes.
- A yes is single-use. Another ticket, a second comment, a new take or a reworded comment each need a fresh one.
- No prompt, no post. In a non-interactive run, stop after step 5 and say it wasn't posted and why.
If they decline, tell them where the files are.
7. Report
Say what was posted and where, or that nothing was. demo.mp4 and
demo-chapters.json stay in $OUT for a later voice-over pass.
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.

