debug SKILL.md skillA
debug from fcakyon/labrat is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fcakyon/labrat/debug@git:20260430.e4e97e0Pins git:20260430.e4e97e0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fcakyon/labrat
- Path
plugin/skills/debug/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260430.e4e97e0, committed Apr 30, 2026
- Size
- 5,263 bytes
- Repository stars
- 452
- License
- MIT
Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list, dmesg, GPU stats, log scrollback, checkpoint state, then states a hypothesis as a hypothesis and runs a smoke before claiming a root cause. Use when the user asks why a run is failing, diverging, OOMing, hanging, slow, producing weird metrics, has crashed, or asks to debug, diagnose, troubleshoot, or investigate a training issue.
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: evidence-before-action investigation The most expensive class of mistake in ML debugging is asserting a cause based on plausibility, then attempting a "fix" that masks the real problem. This skill enforces the discipline of probe → hypothesis → smoke → controls → claim, in that order. The agentic Stop hook routes here from `reason` when an assistant claims a cause without backing tool output. ## When to run The user just said any of: - "why is X failing / diverging / NaN / OOM / hung / slow / crashed" - "the loss is going up", "metrics look weird", "GPU util is 0" - "debug this", "diagnose", "troubleshoot", "investigate this run" - pasted a log excerpt asking what's wrong ## Five-step protocol ### Step 1: cheap probes Before forming any hypothesis, gather the cheap evidence. None of these cost more than a few seconds: **Process state:** ```bash ps aux | grep -E '(python|train|torchrun|accelerate)' | grep -v grep ``` Is the process still running? Zombie? Defunct? Multiple instances? **Kernel / system events:** ```bash dmesg | tail -100 # OOM kills, hardware errors, NFS errors journalctl -xe --since "1 hour ago" | tail -50 ``` **GPU state:** ```bash …
Read the whole file at its exact version.
How to install
mdr add fcakyon/labrat/debug@sha256:4577b9681f1cce5cThe line at the top of this page pins the label git:20260430.e4e97e0, 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_sf22x5gbcp7ajujm)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 30, 2026.
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 (5263 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
fcakyon/labrat · 452 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sf22x5gbcp7ajujm GET https://markdownregistry.com/api/v1/resolve?ref=fcakyon/labrat/debug GET https://markdownregistry.com/api/v1/blob/4577b9681f1cce5cd605f176f545d47c2a8c41bdbb12e192d76ebc34ed063722
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.