debugging is agent-read markdown (skill) from notque/vexjoy-agent: Debugging: guided diagnosis of application bugs, and post-mortem of failed agent sessions..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Debugging Skill
Two modes. Pick one based on the request:
| Signal | Mode |
|---|---|
| Guide me, teach debugging, ask me questions, coaching | **Socratic** |
| What went wrong, post-mortem, stuck loop, session crashed | **Forensics** |
---
## Mode 1: Socratic Debugging
Guide the user to discover root causes through structured inquiry. Never give
the answer -- the user must arrive at it. Read relevant code with Read/Grep/Glob
before formulating questions; code knowledge makes questions precise.
### Question Progression
Follow these 9 phases in order. Each builds evidence for the next.
| Phase | Purpose | Example |
|-------|---------|---------|
| 1. Symptoms | Gap between expected and actual | "What did you expect?" / "What happened instead?" |
| 2. Reproducibility | Deterministic or intermittent | "Can you reproduce this consistently?" |
| 3. Prior Attempts | Avoid retreading | "What have you already tried?" |
| 4. Minimal Case | Reduce search space | "What is the smallest failing input?" |
| 5. Error Analysis | Extract signal from output | "Which part of the error message is most informative?" |
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
A 17 of 17 checks passed. Deterministic, no model, 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 (7695 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
notque/vexjoy-agent · 424 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nr2ftogky42ycw3g
GET https://markdownregistry.com/api/v1/resolve?ref=notque/vexjoy-agent/debugging
GET https://markdownregistry.com/api/v1/blob/68c88799ddf6b26561cace09f03651d56c40bc01adc9ce70c532c4ee27e7d509
Your agent 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.
code-yeongyu/oh-my-openagent · packages/shared-skills/skills/debugging/SKILL.md · Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and…
romiluz13/cc10x · plugins/cc10x/skills/debugging/SKILL.md · Debugging discipline: feedback loop FIRST, root cause before fix, blast radius after
fix. Covers the 10-rung…
iliaal/whetstone · distillery/generated-skills/debugging/SKILL.md · Systematic root-cause debugging: reproduce, investigate, hypothesize, fix with verification. Use when asked to "debug…
calebnewtonusc/chewbacca · skills/debugging/SKILL.md · Find the root cause of a bug instead of guessing at it. Use when the user reports something broken, pastes an error or…
