demo
Skill0 starsChanged 25 days agoMITView on GitHub
Turn an implementation (ticket, PR, branch or feature) into a short, presentation-friendly demo: few words, diagrams, before/after, and a live demo script, as slides, a doc page or markdown. Use on "prepare a demo", "make slides for this feature", "present this implementation", "demo deck", "/demo".
26 other projects use a version of this.
Adopted by
Most recently taken up by
- serhiileniv/skillstheir own version, first seen Nov 8, 2026
- serhiileniv/ccstheir own version, first seen Nov 8, 2026
- NahumLitvin/prismantistheir own version, first seen Nov 8, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- mehboobali98/rmine-skillstheir own version, first seen Nov 1, 2026
- ozerova152-lab/youtube-producertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use review, ship and 1 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.
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★ 324same name
- iamrohithrnair/merman★ 42same name
- eliasstravik/skills★ 22same name
- yarikleto/claude-teacher-plugin★ 9same 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 repository18 other files it gives its agents.
- address-commentsSkill
- deploySkill
- documentSkill
- gather-contextSkill
- implementSkill
- investigateSkill
- observeSkill
- pr-follow-upSkill
- project-profileSkill
- pr-reviewSkill
- qa-planSkill
- qaSkill
- resolve-conflictsSkill
- specSkill
- sprintSkill
- standupSkill
- todoSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Follow ../../shared/policy.md.
- Very specific: line 17
Run dev-skills:gather-context on the ticket/PR, and read the diff (or merged PRs for a feature).
- Very specific: line 35
Use the format asked for, else the profile/defaults ### demo note, else slides.
“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
Follow ../../shared/policy.md. Run dev-skills:project-profile first.
1. Material
Run dev-skills:gather-context on the ticket/PR, and read the diff (or merged PRs for a feature).
Collect: the problem in the user's terms, what changed, how it works, numbers if available (run
dev-skills:observe when the feature is live and impact matters), screenshots via the browser on a
local or staging run when visuals help.
2. Story
5-8 slides or sections, one idea each:
- The problem (who hurt, how).
- What we built (one sentence + a screenshot).
- How it works (diagram: flow or components; Mermaid or SVG).
- Before / after.
- Live demo script: numbered steps with the data to use, what to click, what to point out.
- Impact or early numbers (if any).
- What's next / known limits. At most ~25 words of text per slide; diagrams and visuals carry the rest. Audience is mixed: no code unless the user asks.
3. Format
Use the format asked for, else the profile/defaults ### demo note, else slides.
- slides: a slide-deck artifact type or slides skill if the session offers one, else a .pptx via the pptx skill.
- doc: a doc in the connected docs tool (Notion/Confluence/Docs). Creating it there is a shared-tool write: confirmation list.
- markdown:
demo.mdwith Mermaid diagrams in the work folder.
Output
The link or path, the outline in 5-8 lines, and the demo script.
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.