Find the cause of a bug, failing test, crash, unexpected behavior, or performance regression from reproducible evidence, and fix it when asked. Use when asked to debug or diagnose, or when /work routes a bug here.
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
# Debug with evidence
Find the cause of the reported failure, not a change that hides it. A request to
diagnose allows inspection only; a request to fix also allows a local fix and its
verification. When `/work` sent you here, stop at **Ready to fix** and return the
cause and the proposed fix: `/work` sizes it, and once the fix may proceed, its
build follows step 3 below. Never deploy, experiment on production, or replay
requests with real side effects without permission, and keep credentials out of
logs and shared output.
## 1. Reproduce
Record expected versus actual behavior, inputs, environment, and versions. Facts
only the reporter holds (what exactly they saw, when, who was affected, what they
already did about it) change the next check or the remedy: ask for them in one
message, at the latest with your diagnosis, and record the rest as unknown. Never
advise an action on the damage, such as a refund, without asking whether it was
already done. Then build the
smallest check that reaches the real failure: a test, a command, a request, or a
browser interaction that asserts the reported outcome. Record its output before
changing anything.
…
The line at the top of this page pins the label git:20261101.951d650, 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 (3244 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
firzus/agent-skills · 4 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q7thjsh6a4orkr4m
GET https://markdownregistry.com/api/v1/resolve?ref=firzus/agent-skills/debug
GET https://markdownregistry.com/api/v1/blob/f6578a43c242e1f649dff1daaf4116b982ca4b51f206c1ff7551be9e28c22766
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.
firzus/agent-skills · skills/engineering/authoring/SKILL.md · Use when creating, revising, or reviewing a skill's SKILL.md, supporting references, or templates, or when adjusting…
firzus/agent-skills · skills/engineering/chrome-devtools/SKILL.md · Debug and automate Google Chrome from the shell with the `chrome-devtools` CLI (npm package `chrome-devtools-mcp`)…
firzus/agent-skills · skills/engineering/gamification/SKILL.md · Gamification design for products, apps, and game meta-layers: design an engagement, habit, or retention system; choose…
firzus/agent-skills · skills/engineering/improve-architecture/SKILL.md · Find places where the code is costly to change and propose evidenced refactors that hide complexity behind smaller…
firzus/agent-skills · skills/engineering/instructions/SKILL.md · Use when creating, revising, or reviewing project AGENTS.md files, scoped rules, or other agent-facing documentation…
firzus/agent-skills · skills/engineering/monorepo/SKILL.md · Set up, evolve, and troubleshoot multi-project repositories. Use for workspace structure, cross-package dependencies…
firzus/agent-skills · skills/engineering/runbook/SKILL.md · Write an interactive bash runbook that guides a person through actions only they can take, such as copying credentials…
firzus/agent-skills · skills/engineering/security-review/SKILL.md · Perform source-only security audits of codebases, APIs, services, and applications. Use for security questions, focused…
firzus/agent-skills · skills/engineering/setup-harness/SKILL.md · Set up personal instructions for Codex (app and CLI), Cursor, or Claude Code, with reviewed content, native instruction…
yeachan-heo/oh-my-claudecode · skills/debug/SKILL.md · Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
nanocoai/nanoclaw · .claude/skills/debug/SKILL.md · Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to…
agentic-community/mcp-gateway-registry · .claude/skills/debug/SKILL.md · Debug issues in the MCP Gateway Registry using first-principles thinking. Invoke when something is broken, timing out…
suboss87/fdeops · skills/debug/SKILL.md · Investigate a failure, regression or incorrect result in an integration or application, even before it can be…
rsmdt/the-startup · plugins/start/skills/debug/SKILL.md · Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
ericrisco/rsc-harness · skills/debug/SKILL.md · Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be…
fcakyon/labrat · plugin/skills/debug/SKILL.md · Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list…
