Safe Debug (RigorPilot)
Conservative diagnosis for deep-learning failures — tracebacks, CUDA OOM, NaN loss, checkpoint issues — diagnose first, then propose the smallest fix with explicit approval before any mutation
- What
- Conservative diagnosis for deep-learning failures — tracebacks, CUDA OOM, NaN loss, checkpoint issues — diagnose first, then propose the smallest fix with explicit approval before any mutation
- Cost
- Free
- Needs
- none — a concrete failure to diagnose (traceback, terminal error, CUDA OOM, NaN loss, checkpoint issue) is what you bring at use time; the skill diagnoses first and requires explicit approval before any patch.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the RigorPilot "Rigor Debug / Rigor Audit" skill for deep-learning research work. It applies when you paste a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom or training failure and want conservative diagnosis before any patching. The discipline is diagnose-first: no repository modification by default; if a patch is needed, the smallest fix is proposed and explicit approval is required first; savepoint or branch creation is escalated before medium- or high-risk changes. And a hard conceptual line is drawn: a debug fix is not automatically a research contribution — if it changes experiment meaning or comparability, the skill says so explicitly. Outputs are `debug_outputs/DIAGNOSIS.md`, `debug_outputs/PATCH_PLAN.md` and `debug_outputs/status.json`. Not for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization. By @lllllllama, listed here with credit to its creator. Honest caveats: diagnosis needs concrete failure evidence — a vague "it doesn't work" gets you little; human approval is a hard gate, so don't expect autonomous repair; a flagged root cause remains a diagnosis until a run confirms it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none — a concrete failure to diagnose (traceback, terminal error, CUDA OOM, NaN loss, checkpoint issue) is what you bring at use time; the skill diagnoses first and requires explicit approval before any patch. Install "Safe Debug (RigorPilot)" for me. The RigorPilot conservative debugging skill for deep-learning failures: diagnosis before any patching, smallest-fix proposals, explicit human approval required, and debug fixes clearly separated from research contributions. Repository: https://github.com/lllllllama/rigorpilot-skills/blob/main/skills/safe-debug/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "rigorpilot-safe-debug". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.