<ROLE_NAME> SKILL.md skillA
<ROLE_NAME> from xnoname79/unity-agent-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@git:20261102.b025e37Pins git:20261102.b025e37 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- xnoname79/unity-agent-orchestrator
- Path
templates/playbooks/bugfix/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.b025e37, committed Nov 2, 2026
- Size
- 2,000 bytes
- Repository stars
- 2
- License
- MIT
Sub-agent playbook — bug fix. ACTIVATE on EVERY message reaching this session. Reproduce first, find the root cause with runtime evidence, fix it, verify on the same reproduction.
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
# <ROLE_NAME> — bug fix You are a sub-agent. A director gave you one bug. You work alone in a git worktree on your own branch. An independent verifier checks the `Done means` contract after you finish. ## Steps — do every one, in order 1. **Reproduce first.** Make the bug happen on the interface where it was reported, before reading any fix-shaped code. Save the exact steps and the observed output. Cannot reproduce? Stop and report that, with what you tried — do not fix a bug you have not seen. 2. **Competing causes.** List at least two plausible causes. Rule them in or out with runtime evidence (logs, a debugger, a print, a narrowed input), not by reading code and guessing. 3. **Root cause.** Fix the mechanism, not the symptom. If the fix is a guard around a value that should never be wrong, keep going: why is it wrong? 4. **Regression check.** Add a test that fails before the fix and passes after, when the project has a cheap place for one. Otherwise keep the reproduction script. 5. **Verify on the same reproduction** from step 1, on the same interface. Show it now behaves. …
Read the whole file at its exact version.
How to install
mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@sha256:aab20c52fcad4255The line at the top of this page pins the label git:20261102.b025e37, 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_nikwhgmfs57tv7cr)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 2, 2026.
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 (2000 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
xnoname79/unity-agent-orchestrator · 2 stars · license MIT · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_nikwhgmfs57tv7cr GET https://markdownregistry.com/api/v1/resolve?ref=xnoname79/unity-agent-orchestrator/<ROLE_NAME> GET https://markdownregistry.com/api/v1/blob/aab20c52fcad425504a1fcc07d8d06935ce234c51d0b57ed5a43de3116c473d5
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 xnoname79/unity-agent-orchestrator
Every file in xnoname79/unity-agent-orchestrator