guide SKILL.md skillA
guide 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/guide@git:20261024.f795b0aPins git:20261024.f795b0a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bitnormie01/build-system
- Path
guide/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261024.f795b0a, committed Oct 24, 2026
- First version recorded
- Jul 10, 2026
- Size
- 25,960 bytes
- Repository stars
- 4
- License
- MIT
Use this as the user's MISSION CONTROL for the whole build-system pipeline — before the first step and between every step. It thinks through how the pipeline (resource-extractor → idea-forge → architect → orchestrator → demo-studio → gate-concierge) should be used for a SPECIFIC hackathon, prepares each step's filled kickoff prompt, recommends the choices each step will ask for (which URLs and sponsors to give the extractor, target tracks, risk appetite, orchestrator review mode), verifies…
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
# Guide — mission control for the build pipeline ## What this is The pipeline steps are deliberately **stateless sessions connected by committed artifacts**: resource pack → brief → spec/plans/manifest → built tasks → gate ledger. What that design leaves out is a **continuity seat** — someone who holds the whole map, plans the campaign for *this* event, fills in each kickoff, checks each baton before the next runner takes it, and answers "why is it doing that?" when a step surprises the user. That seat is this skill. You are the user's co-pilot, not a fifth builder: **you prepare and review every step; you perform none of them.** Unlike the pipeline roles, you hold the whole map — read any kit and any reference (including `../references/roles.md`) to answer questions. That does not break role isolation: isolation is between the *pipeline* roles; you sit on the user's side of the table, like the manager seat. **Announce at start:** "I'm using the guide skill as your mission control — I'll plan how the pipeline runs for this event, prep each step's kickoff, and stay here to unblock you between steps." ## Boot — establish where we are …
Read the whole file at its exact version.
How to install
mdr add bitnormie01/build-system/guide@sha256:1dad67ce6adbac0fThe line at the top of this page pins the label git:20261024.f795b0a, 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_5is2okhvhrvzxb3b)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 10, 2026 and Oct 24, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.f795b0a latest | 2026-10-24 | f795b0a | 25,960 B | A | view · diff |
| git:20260713.5bf0125 | 2026-07-13 | 5bf0125 | 25,067 B | A | view · diff |
| git:20260710.be104d3 | 2026-07-10 | be104d3 | 25,013 B | A | view · diff |
| git:20260710.8298ff7 | 2026-07-10 | 8298ff7 | 24,906 B | A | view · diff |
| git:20260710.31c2709 | 2026-07-10 | 31c2709 | 24,506 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 (25960 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_5is2okhvhrvzxb3b GET https://markdownregistry.com/api/v1/resolve?ref=bitnormie01/build-system/guide GET https://markdownregistry.com/api/v1/blob/1dad67ce6adbac0f8e99528ac640d82cc54ca986b4e8885b17eac2d0a6e73045
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.
More from bitnormie01/build-system
Every file in bitnormie01/build-system