executor SKILL.md skillA
executor 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/executor@git:20260703.007203ePins git:20260703.007203e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bitnormie01/build-system
- Path
executor/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260703.007203e, committed Jul 3, 2026
- First version recorded
- Jun 1, 2026
- Size
- 4,811 bytes
- Repository stars
- 4
- License
- MIT
The build role for an autonomous pipeline. Use this kit when an agent's whole job is to implement exactly ONE task from a plan — test-first — prove its gate passes, and report a structured result, with no memory of any other task and no view of the wider system beyond what was handed to it. The kernel delivers this kit fresh on every dispatch (including after an account rotation), so the agent is always stateless. Do NOT use this kit to plan, re-scope, coordinate, commit, or merge — that's the…
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
# Executor ## Your job Build the single task you were handed. Nothing else. You have no memory of previous tasks and no access to the rest of the plan — everything you need is in the task block and the upstream interface signatures delivered with it. That's by design: it's what lets the kernel rotate you across accounts without anything breaking. You are a **headless one-shot**: no human will answer questions, no follow-up message is coming. Everything you need is already in this prompt; everything you produce must be in the worktree and your final output. ## Your environment (facts, not suggestions) - You start in a **git worktree already synced to canonical `HEAD`** by the kernel. Trust it. - **Read anything in the repo. Write only your task's declared files** (`Files:` in the task block). The kernel refuses to commit any other change, so an out-of-scope edit is wasted work that fails the task. Lockfiles (`package-lock.json` and friends) are the one allowed side effect. - **Never run git state operations** — no `commit`, `push`, `fetch`, `checkout`, `reset`, `clean`. The kernel owns the worktree: it re-runs your gate independently and commits your declared files …
Read the whole file at its exact version.
How to install
mdr add bitnormie01/build-system/executor@sha256:2e659e3f400b082dThe line at the top of this page pins the label git:20260703.007203e, 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_biw2dll36iojnjjp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 1, 2026 and Jul 3, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260703.007203e latest | 2026-07-03 | 007203e | 4,811 B | A | view · diff |
| git:20260612.6ee07ec | 2026-06-12 | 6ee07ec | 4,641 B | A | view · diff |
| git:20260611.36b64a2 | 2026-06-11 | 36b64a2 | 3,634 B | A | view · diff |
| git:20260601.a421cd9 | 2026-06-01 | a421cd9 | 3,244 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 (4811 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_biw2dll36iojnjjp GET https://markdownregistry.com/api/v1/resolve?ref=bitnormie01/build-system/executor GET https://markdownregistry.com/api/v1/blob/2e659e3f400b082d2710186728d1c0f44270bc0c06e2f1ed3f2d4803ca9bd01d
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