ai-debug SKILL.md skillA
ai-debug from arcasilesgroup/ai-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arcasilesgroup/ai-engineering/ai-debug@git:20260926.b0fd9cfPins git:20260926.b0fd9cf in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arcasilesgroup/ai-engineering
- Path
skills/ai-debug/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.b0fd9cf, committed Sep 26, 2026
- First version recorded
- Sep 1, 2026
- Size
- 3,966 bytes
- Repository stars
- 62
- License
- Apache-2.0
Finds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-verify. Not for exploring an unfamiliar area — use /ai-explore.
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
# ai-debug — find the cause, not the symptom ## What it produces A named cause at `file:line`, a check that fails because of it, and only then a fix. ## Steps 1. Reproduce it. If you cannot reproduce it, say so plainly and stop guessing: the next useful thing is a way to reproduce it, not a change. 2. Read the failing output in full. The first error is usually the real one and the rest are its consequences; the last error is the one people paste. 3. Name a cause you can point at. `file:line`, and one sentence on why that line produces this symptom. "Probably a race" is not a cause. If two causes are plausible, say which observation would tell them apart, then go and make that observation. 4. Before the fix, write the check that fails for this reason. A fix with no failing check before it is a change with an opinion attached. 5. Fix the cause, at the place all the callers go through. Patching the one path the report named leaves every sibling caller broken, and the shared fix is usually the smaller diff. 6. Run the check. Then run the suite. Then say what you changed and why it fixes the cause you named, not the symptom that was reported. …
Read the whole file at its exact version.
How to install
mdr add arcasilesgroup/ai-engineering/ai-debug@sha256:c2c10b826a63eb92The line at the top of this page pins the label git:20260926.b0fd9cf, 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_gnuxejd3h54iswp2)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 1, 2026 and Sep 26, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.b0fd9cf latest | 2026-09-26 | b0fd9cf | 3,966 B | A | view · diff |
| git:20260914.793714f | 2026-09-14 | 793714f | 4,048 B | A | view · diff |
| git:20260910.d021330 | 2026-09-10 | d021330 | 4,051 B | A | view · diff |
| git:20260901.deb68d3 | 2026-09-01 | deb68d3 | 3,908 B | A | view · diff |
| git:20260901.dca22e5 | 2026-09-01 | dca22e5 | 1,748 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 (3966 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
arcasilesgroup/ai-engineering · 62 stars · license Apache-2.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gnuxejd3h54iswp2 GET https://markdownregistry.com/api/v1/resolve?ref=arcasilesgroup/ai-engineering/ai-debug GET https://markdownregistry.com/api/v1/blob/c2c10b826a63eb92485acfedfc7ee3f079b245ffb33224d115c7804bc928915c
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.