diagnose SKILL.md skillA
diagnose from xopcai/xopc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add xopcai/xopc/diagnose@git:20260916.b7327d9Pins git:20260916.b7327d9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- xopcai/xopc
- Path
skills/engineering/diagnose/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260916.b7327d9, committed Sep 16, 2026
- First version recorded
- May 10, 2026
- Size
- 7,363 bytes
- Repository stars
- 40
- License
- MIT
Disciplined reproduce → minimise → hypothesise → instrument → fix loop for hard bugs and performance regressions.
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
# Diagnose A discipline for hard bugs. Skip phases only when explicitly justified. When exploring the codebase, use the project's domain glossary to get a clear mental model of the relevant modules, and check ADRs in the area you're touching. ## Phase 1 — Build a feedback loop **This is the skill.** Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you. Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.** ### Ways to construct one — try them in roughly this order 1. **Failing test** at whatever seam reaches the bug — unit, integration, e2e. 2. **Curl / HTTP script** against a running dev server. 3. **CLI invocation** with a fixture input, diffing stdout against a known-good snapshot. 4. **Headless browser script** (Playwright / Puppeteer) — drives the UI, asserts on DOM/console/network. …
Read the whole file at its exact version.
How to install
mdr add xopcai/xopc/diagnose@sha256:786d45a95d5b939fThe line at the top of this page pins the label git:20260916.b7327d9, 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_yso2xajodarvdlpe)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 10, 2026 and Sep 16, 2026, about one every 65 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.b7327d9 latest | 2026-09-16 | b7327d9 | 7,363 B | A | view · diff |
| git:20260618.8ea2a18 | 2026-06-18 | 8ea2a18 | 7,004 B | A | view · diff |
| git:20260510.b4830d5 | 2026-05-10 | b4830d5 | 7,163 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 (7363 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
xopcai/xopc · 40 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yso2xajodarvdlpe GET https://markdownregistry.com/api/v1/resolve?ref=xopcai/xopc/diagnose GET https://markdownregistry.com/api/v1/blob/786d45a95d5b939f5a37df8e69d30db8414c84af7e1cac1657526f5131eae817
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.