bug-investigate SKILL.md skillA
bug-investigate from kardebadas/claude-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kardebadas/claude-plugin/bug-investigate@git:20260901.85e6446Pins git:20260901.85e6446 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kardebadas/claude-plugin
- Path
plugins/superb/skills/bug-investigate/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260901.85e6446, committed Sep 1, 2026
- Size
- 3,773 bytes
- Repository stars
- 3
- License
- Apache-2.0
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing — that is superb:bug-fix.
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
# Bug Investigate ## Overview Finds the root cause of a bug and reports it. **That is the whole job.** No plan, no fix, no edits. Knowing what is wrong is often the thing that is actually needed — because the fix is obvious once you know, because the decision about *whether* to fix is someone else's, or because the answer changes what gets built rather than what gets patched. **This is the same investigation `superb:bug-fix` runs as its first step.** The difference is where it stops. If you already know you want the bug fixed end to end, use `superb:bug-fix` and let it carry the result into a plan. ## Step 0 — Assemble the report The investigator needs five things, and the invocation argument usually supplies one or two: | Field | Example | | ----- | ------- | | Symptom | "uploads over ~5MB fail silently" | | Reproduction | the steps, or `unknown` | | Error text | stack trace, log line, or `none surfaced` | | Affected surface | endpoint, screen, command, job | | Last known good | a date, a release, a commit, or `never worked` | Ask for whatever is missing in **one batched question**, not five. `unknown` is a …
Read the whole file at its exact version.
How to install
mdr add kardebadas/claude-plugin/bug-investigate@sha256:780d454eba1f5dfbThe line at the top of this page pins the label git:20260901.85e6446, 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_draym3g3r7334qpv)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 1, 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 (3773 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
kardebadas/claude-plugin · 3 stars · license Apache-2.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_draym3g3r7334qpv GET https://markdownregistry.com/api/v1/resolve?ref=kardebadas/claude-plugin/bug-investigate GET https://markdownregistry.com/api/v1/blob/780d454eba1f5dfb85ff4fd3625e9fa1e19f03653c734c98858599c406df449f
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.