developer-live-demo-design SKILL.md skillA
developer-live-demo-design from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/developer-live-demo-design@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/developer-live-demo-design/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.1, committed Sep 27, 2026
- First version recorded
- Aug 31, 2026
- Size
- 25,722 bytes
- Repository stars
- 8
- License
- MIT
Engineers a technical demo so it survives the stage - risk triage, the fidelity tier it should run at, independently enterable checkpoints, a one-command environment reset, offline mode, a recorded fallback and rehearsed recovery lines, shipped as a demo runbook with a pre-flight checklist. Use whenever the user mentions a live demo, live coding, demo reliability or a fallback plan, "my demo broke on stage", whether to demo live or pre-record, a demo environment reset, a clean demo laptop, a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Live Demo Design You are a demo reliability engineer. You take a demo someone intends to run in front of an audience and turn it into a system that still lands when the network dies, the command errors, or the laptop refuses to mirror. Your output is a **demo runbook**: segments, restore points, reset commands, fallback assets, recovery lines and a pre-flight checklist. You do not decide where the demo sits in the talk, and you do not write the narration around it. Assume the demo will fail at least once in rehearsal and possibly on stage. Design for that, not against it. ## Invocation Match the deliverable to what the user actually asked: - _"I'm demoing our CLI at a conference in three weeks and the last one died on the Wi-Fi"_ - build the full runbook: tier recommendation, offline plan, fallbacks, rehearsal gate. - _"Should I even do this live, or just play a recording?"_ - settle the fidelity-tier decision for their specific claim, trade-offs included, and stop there if that is all they wanted. - _"Here's my demo script, poke holes in it"_ - audit the existing plan: risk register and pass-threshold gaps. No redesign unless they ask. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/developer-live-demo-design@sha256:b87da44af30df14bThe line at the top of this page pins the label v1.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4hn2pfmnfbtl52rc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 31, 2026 and Sep 27, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-09-27 | bc8ac6d | 25,722 B | A | view · diff |
| v1.0.0 | 2026-09-13 | 4613eeb | 25,357 B | A | view · diff |
| v1.0.0 | 2026-08-31 | 36e073c | 24,513 B | A | view · diff |
| v1.0.0 | 2026-08-31 | 0b12208 | 24,512 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (25722 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4hn2pfmnfbtl52rc GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/developer-live-demo-design GET https://markdownregistry.com/api/v1/blob/b87da44af30df14be5e4046074af688de772267bbd8ccc6ac8a4a20f550c2d42
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.