demo-studio SKILL.md skillA
demo-studio from bitnormie01/build-system is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bitnormie01/build-system/demo-studio@git:20260713.5bf0125Pins git:20260713.5bf0125 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bitnormie01/build-system
- Path
demo-studio/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260713.5bf0125, committed Jul 13, 2026
- First version recorded
- Jul 9, 2026
- Size
- 18,568 bytes
- Repository stars
- 4
- License
- MIT
Use this at Step 2.5 — AFTER the orchestrator reports the build green, before the submission is filed — to produce the hackathon's demo video autonomously on the user's machine: it writes a scene-by-scene demo script from the brief/spec/event.md, records the built app scene-by-scene (Playwright screencast for browser scenes, ffmpeg gfxcapture/ddagrab for native/wallet-popup scenes), narrates with TTS and word-timed captions, assembles with Remotion, runs a frame-level QC loop, has the user…
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
# Demo Studio — Step 2.5: the demo video, recorded and assembled autonomously ## What this is Every hackathon submission needs a 2–5 minute demo video, and hand-producing it — script, record, narrate, caption, edit, upload — costs hours at the worst possible time. The kit has automated everything up to here: the build is green, and the architect's `docs/gates/submission-draft.md` carries a `TBD-post-build: demo video URL` waiting to be filled. This seat fills it. It drives the built app through a scene-by-scene script, captures each scene, assembles a captioned narrated cut with Remotion, and — only after the watch gate (Stage 7) and the upload consent — uploads it. It is a **user-side seat** (like the guide and the gate-concierge): it runs on the user's machine with their granted tooling, it **never self-triggers**, and its two outward actions — running a foreground recording session and publishing the video — are **consented gates**. Quality comes from gates, not hope: every scene has a pass/fail assertion and a bounded retake budget, every render passes a frame-level QC loop, and **the user watches the final cut before anything is published** …
Read the whole file at its exact version.
How to install
mdr add bitnormie01/build-system/demo-studio@sha256:31fa3834aad965bbThe line at the top of this page pins the label git:20260713.5bf0125, 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_mjnxvegavlbdq32z)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 9, 2026 and Jul 13, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260713.5bf0125 latest | 2026-07-13 | 5bf0125 | 18,568 B | A | view · diff |
| git:20260710.be104d3 | 2026-07-10 | be104d3 | 17,266 B | A | view · diff |
| git:20260710.31c2709 | 2026-07-10 | 31c2709 | 17,210 B | A | view · diff |
| git:20260710.401faad | 2026-07-10 | 401faad | 14,514 B | A | view · diff |
| git:20260709.a31a432 | 2026-07-09 | a31a432 | 14,171 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 (18568 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
bitnormie01/build-system · 4 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mjnxvegavlbdq32z GET https://markdownregistry.com/api/v1/resolve?ref=bitnormie01/build-system/demo-studio GET https://markdownregistry.com/api/v1/blob/31fa3834aad965bb449000aa7daa59de4171aa1ea4b05bf41d82d95793976f05
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.