mcpbeat Sign in

Safe Debug Agent Skill

by lllllllama

Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

2k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
484
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/lllllllama/RigorPilot-Skills --skill safe-debug

What comes with it

7 565 bytes besides the instruction
agents/openai.yaml
references/debug-policy.md
scripts/safe_debug.py

The instruction itself

6 sections, as written by the author

safe-debug

Use this as the Rigor Debug / Rigor Audit skill. The installed slug remains

safe-debug for compatibility.

Use the shared operating principles in

../ai-research-reproduction/references/agent-operating-principles.md; this skill should guide

conservative diagnosis without blocking the model from finding the local root

cause.

When to apply

  • The user provides a traceback, terminal error, or concrete training or inference failure symptom.
  • The user wants diagnosis, root-cause narrowing, and minimal patch suggestions before code is changed.
  • The user wants a safe debug flow with explicit human approval before mutation.

When not to apply

  • When the user wants a broad repository walkthrough without an active failure.
  • When the task is speculative experimentation or code adaptation.
  • When the user is asking for a large refactor or readability rewrite.

Clear boundaries

  • Diagnose first.
  • Do not modify repository code by default.
  • If a patch is needed, propose the smallest fix and require explicit approval first.
  • Escalate savepoint or branch creation before medium-risk or high-risk changes.
  • A debug fix is not automatically a research contribution; if it changes

experiment meaning or comparability, say so explicitly.

Output expectations

  • debug_outputs/DIAGNOSIS.md
  • debug_outputs/PATCH_PLAN.md
  • debug_outputs/status.json

Notes

Use references/debug-policy.md, ../ai-research-reproduction/references/research-rigor-principles.md, and the shared ../ai-research-reproduction/references/research-pitfall-checklist.md.

How to use it

Copy the folder

Take lllllllama/safe-debug from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.