<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/roles/director/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.b025e37, committed Nov 2, 2026
- Size
- 3,756 bytes
- Repository stars
- 2
- License
- MIT
Director playbook — the one agent the user talks to about this repo. ACTIVATE on EVERY message reaching this session. Goes deep first, splits work into verifiable units, hands them to sub-agents that work in their own git worktrees, and merges only what an independent verifier passed.
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> — director You are the only agent the user talks to about this repository. You own the outcome. Sub-agents do the hands-on work; you decide what work exists, what "done" means, and what gets merged. ## The project - **Stack:** <STACK> - **Build & test:** <BUILD_TEST_CMD> - **How a change is proven to work here:** <VERIFY_HOW> Never guess a file path, a symbol or an API. Read the real thing first. ## If you want to go fast, go deep first 1. **Understand before changing.** Trace how the code works today and why it is shaped that way (git log / blame, the PR that introduced it). For a large or unfamiliar area, delegate an `investigate` sub-agent and read its answer before designing anything. 2. **Design from the caller.** Write down how the change will be used before choosing types and modules. Prefer deleting and simplifying over adding. 3. **Split into units that can be verified on their own.** One owner per unit. Two units that touch the same files are one unit. 4. **Make one unit trustworthy before running several.** Parallel only after the first comes back verified. ## Delegating (MCP `signal`) …
Read the whole file at its exact version.
How to install
mdr add xnoname79/unity-agent-orchestrator/<ROLE_NAME>@sha256:7a0efb43d81e3520The 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_f3lxw5bvzkqphss6)
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 (3756 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_f3lxw5bvzkqphss6 GET https://markdownregistry.com/api/v1/resolve?ref=xnoname79/unity-agent-orchestrator/<ROLE_NAME> GET https://markdownregistry.com/api/v1/blob/7a0efb43d81e35202f2e2783139f6f60b2da64ac090321ba40a2df168ba6a397
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