Investigate-first debugging discipline
Diagnose ambiguous failures with evidence-ranked hypotheses before touching a single line of code
- What
- Diagnose ambiguous failures with evidence-ranked hypotheses before touching a single line of code
- Cost
- Free
- Needs
- nothing — reference lookup only; no license declared in the source repo, so read it yourself before reusing its content
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a short pointer to @juliusbrussee's investigate-first method: a five-rule debugging discipline for ambiguous failures — separate the observed symptom from the inferred cause, trace inputs, state transitions, ownership boundaries and failure output, rank hypotheses by evidence and cheap falsification value, and make no fix until one credible mechanism explains the evidence, stopping exploration the moment the cause or the exact blocker is named. Honest caveats: no license declared in the repository — license unknown, so this is a short fiche linking to the source, without reusing its content; it is a process guide only, it ships no tooling or scripts. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Investigate-first debugging discipline is a free Muse skill that diagnoses ambiguous failures with evidence-ranked hypotheses before touching a single line of code. Its five-rule discipline separates the observed symptom from the inferred cause, traces inputs, state transitions, ownership boundaries and failure output, and ranks hypotheses by evidence before acting.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 2e08b91Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: nothing — reference lookup only; no license declared in the source repo, so read it yourself before reusing its content Install "Investigate-first debugging discipline" for me. Fetch the SKILL.md from the source repository into a temporary folder, review it for anything suspicious, and report in two or three sentences what the investigate-first method covers (separating symptoms from inferred causes, tracing inputs and state transitions, evidence-ranked hypotheses, no fix until one credible mechanism explains the evidence) so I can apply the discipline to my own debugging. Do not copy the guide's content into my project — this is a reference lookup only. Repository: https://raw.githubusercontent.com/juliusbrussee/caveman/2e08b9177c07bb7249a8a2d1a6758e5db281d002/skills/investigate-first/SKILL.md Pinned version: install the code at commit 2e08b9177c07bb7249a8a2d1a6758e5db281d002 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 2e08b91 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.