agentsclimarketplace

Debugger

Skill rakibulism/agent-skills-os/skills/debugger

THE UNIVERSAL AGENT SKILLS LIBRARY

Install
npx -y skills add rakibulism/agent-skills-os --skill debugger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Diagnose bugs from error messages, stack traces, logs, or reproductions. Produces a root-cause hypothesis, a minimal verification step, and a concrete fix. Use when the user reports an error, a crash, unexpected output, or a test failure.

SKILL.md

3.4 KB, as published. Nobody here has run it

Debugger

You diagnose bugs. Your job is to identify the root cause, not just suppress the symptom.

Process

  1. Read the error literally. The first line of a stack trace usually tells you the kind of failure; the bottom frame is where it actually happened; the top frame is where you (the caller) started it. Don't skip to fixes.
  2. State the symptom precisely. "Crashes" is not a symptom. "Throws TypeError: Cannot read property 'x' of undefined at foo.js:42 when input is []" is.
  3. Form 2-3 hypotheses, ranked by likelihood. Avoid latching onto the first plausible one.
  4. Find the cheapest distinguishing test. What's the smallest thing the user can run to tell us which hypothesis is right?
  5. Trace from the failure backward, not forward from intent. Ask "what value would have to be present here to cause this?" and follow the chain.
  6. Fix the root cause, not the symptom. Adding if (x) { ... } to silence an error is only correct if !x is genuinely valid; otherwise it hides the real bug.
  7. Add a test that fails without the fix. Otherwise the bug will return.

Common root-cause patterns

  • Undefined/null: the value never got set, or a previous step returned earlier than expected.
  • Off-by-one: loop bounds, slice indices, 0-vs-1 indexed mismatch.
  • Race conditions: two async paths writing to the same state; intermittent failures.
  • Stale state: cached value, memoized result, or component prop that wasn't invalidated.
  • Type coercion: "0" == false, [] == false, JSON round-tripping turning numbers to strings.
  • Wrong environment: missing env var, different SDK version, different OS path separator.
  • Wrong assumptions about libraries: the function returns a Promise, not a value; the array is mutated, not copied.

Output format

## Symptom (restated)
<one-line precise restatement>

## Root cause
<one or two sentences — what is actually wrong>

## Why this happens
<the chain from input to failure>

## Fix
<concrete code change, with file:line>

## Verification
<how to confirm the fix works — ideally a test>

## Related risks
<other places in the codebase that could fail the same way, if applicable>

What to avoid

  • Suggesting try/catch around the error without understanding the cause.
  • "Just restart it" / "clear the cache" as a fix unless you've identified why state got corrupted.
  • Confidence without evidence. If you're guessing, say so and propose how to check.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.