Example skill scaffold. Replace this with a real, project-specific procedural playbook. The description must clearly state WHEN to use the skill (trigger phrases and scope) so the model can match it to user intent. USE FOR: <list the situations this skill applies to>. DO NOT USE FOR: <list out-of-scope situations and point to the right skill>.
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
# Example Skill
Describe the repeatable procedure here. Skills are loaded on demand when the
`description` above matches the user's request.
## When to Use
- Trigger phrase 1
- Trigger phrase 2
## Steps
1. Step one — what to read or check first.
2. Step two — the action to take.
3. Step three — how to validate the result.
## Guardrails
- State any safety boundaries (no destructive actions without confirmation).
- Reference related skills for out-of-scope work.
## Output
- Describe what the skill produces and where it is saved.
The line at the top of this page pins the label git:20260626.368d116, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (949 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
GitHub
zhiming-dev/roster · 12 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7q2dxr6zeooh6ufs
GET https://markdownregistry.com/api/v1/resolve?ref=zhiming-dev/roster/example-skill
GET https://markdownregistry.com/api/v1/blob/9145f8fc03ce35e9a8c61984b8c885f47934e5e08b4153d04071a4505ca53b51
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.
zhiming-dev/roster · coder-agent/coder-runner/SKILL.md · Implement one task on a feature branch. Use when: the Planner has dispatched a `task_assignment` to the Coder role…
zhiming-dev/roster · e2e-agent/e2e-runner/SKILL.md · Run E2E test suites using playwright-cli. Use when: running test suites, executing smoke tests, running E2E/bug-bash…
zhiming-dev/roster · planner-agent/planner-runner/SKILL.md · The Planner's operating procedure. Use when: turning a principal goal into a Plan; revising a plan after rejection…
zhiming-dev/roster · qa-agent/qa-runner/SKILL.md · Validate and fact-check another agent's output against evidence and the task's success criteria. Use when: verifying a…
zhiming-dev/roster · researcher-agent/researcher-runner/SKILL.md · Procedure the Researcher agent follows to answer a question with web search + page fetch: plan queries, search, open…
zhiming-dev/roster · reviewer-agent/reviewer-runner/SKILL.md · Review a diff against a task's success criteria. Use when: a `task_assignment` for role `reviewer` lands; you need to…
zhiming-dev/roster · shared/approval-gate/SKILL.md · Classify a proposed action's risk tier (T0–T4), apply the gate policy, and (if required) summarize the proposal into a…
zhiming-dev/roster · shared/council/SKILL.md · Run a cross-model deliberation: pose the same question to multiple model bindings (e.g. Claude, GPT, Gemini), have them…
zhiming-dev/roster · shared/provenance/SKILL.md · Append a structured event to the run's provenance log. Every agent calls this for every meaningful state transition…
anthropics/claude-plugins-official · plugins/example-plugin/skills/example-skill/SKILL.md · This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template"…
serpro69/claude-toolbox · kodex-plugin/skills/diff-skill/evals/known-degradation/test-files/before/SKILL.md · An example skill for testing diff-skill evaluation.
serpro69/claude-toolbox · klaude-plugin/skills/diff-skill/evals/known-degradation/test-files/before/SKILL.md · An example skill for testing diff-skill evaluation.
serpro69/claude-toolbox · kodex-plugin/skills/diff-skill/evals/known-degradation/test-files/after/SKILL.md · An example skill for testing diff-skill evaluation.
serpro69/claude-toolbox · klaude-plugin/skills/diff-skill/evals/known-degradation/test-files/after/SKILL.md · An example skill for testing diff-skill evaluation.
