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

Debug

skill-srrenks-prometheus-ai-debug · by SrRenks

Find and fix a bug systematically: reproduce it, isolate the failing path, verify assumptions, fix the root cause, and keep a regression test. Use when something is broken and the cause is not obvious, when an earlier fix did not hold, or when the user reports a bug with no known cause.

— No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-srrenks-prometheus-ai-debug

✓ 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-srrenks-prometheus-ai-debug)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 8d 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 Debug? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Work the bug down instead of guessing at it. Rules and tactics: ~/.config/agent-config/core/docs/debugging.md.

  1. Reproduce - get the smallest scenario that fails every time, and capture the exact dependency versions, logs, and stack traces.
  2. Isolate - narrow to the smallest failing unit, commenting out or stubbing half at a time. Write a failing test that pins the behavior before touching the fix.
  3. Verify assumptions - check configuration, dependency versions, and the data. Reproduce against a known-good dataset to rule data corruption out.
  4. Fix the cause, not the symptom - the minimal change that makes the failing test pass. No drive-by refactors in the same edit.
  5. Keep the regression test - the failing test stays, or gets an equivalent that would have caught this class of bug.
  6. Post-mortem note - if the bug reached production or cost more than the time-box, record the root cause and what would have caught it earlier.

Deliverable: the fixed cause, the regression test, and a short report of what it was and why it happened.

Stop condition: report the root cause and the fix, or stop after three attempts on a simple issue and report what you ruled out.

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.

Versions

  • v0.1.0 Imported from the upstream source.