AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Systematic Debugging

skill-archive228-loopkit-systematic-debugging · by Archive228

Use for ANY bug, test failure, crash, or unexpected behavior. Forces

↗ Repository
— No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-archive228-loopkit-systematic-debugging

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-archive228-loopkit-systematic-debugging)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Systematic Debugging? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Systematic Debugging

The single most expensive agent failure: seeing an error and immediately generating a "fix" based on the error type, without reading what actually happened. Don't.

The loop

  1. Read the whole error. The entire message and stack trace. A TypeError can mean a

hundred different things — the trace tells you which one. Quote the exact line that throws.

  1. Reproduce it first. If you can't reproduce it, you can't verify a fix. Write the

smallest input that triggers it. "I think this fixes it" is gambling, not debugging.

  1. Form one hypothesis, name it. "I think the value is null because the upstream call

returns 204 with no body." State it before you touch anything.

  1. Change one thing. Test. Repeat. If you change three things and it works, you don't

know which one fixed it — and the other two may have added new bugs.

  1. Fix the root cause, not the symptom. A null check that hides a null is not a fix.

Find why it's null. The underlying bug will resurface differently if you only patch the crash.

Stop conditions

  • If 3 hypotheses fail, STOP and report: what you tried, what you saw, what you suspect.

"I've tried X and Y, here's the output, I think it's Z but I'm not sure" beats 20 silent random attempts.

  • Never add a workaround you don't understand.

Output

End with: the root cause (one sentence), the minimal fix, and the test that now proves it.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills