Skills debugger

📦

debugger

Name: debugger
Author: shubhamsaboo

v1.0.0 Content revision r1 Safe ⚙️ External commands

Debug Software Failures Systematically

Bugs waste engineering time when symptoms hide the real cause. This skill guides Claude, Codex, and Claude Code through structured investigation, hypothesis testing, fixes, and prevention.

Supports: Claude Codex Code(CC)

🥈 80 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "debugger" from https://skillstore.io/skills/shubhamsaboo-debugger.md and its manifest at https://skillstore.io/api/skills/shubhamsaboo-debugger/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/shubhamsaboo-debugger.md Signed manifest GET /api/skills/shubhamsaboo-debugger/manifest Signed lockfile GET /api/skills/shubhamsaboo-debugger/lockfile

Test it

Using "debugger". A web API returns intermittent internal server errors during traffic spikes.

Expected outcome:

The response lists likely causes such as connection pool exhaustion, missing awaits, and unhandled promise rejections. It gives log checks and verification steps.

Using "debugger". A feature worked yesterday but fails after several recent commits.

Expected outcome:

The response proposes a regression search, a minimal test case, and evidence needed to isolate the change that introduced the bug.

Using "debugger". A user interface shows stale data after saving changes.

Expected outcome:

The response separates cache, state, and API timing hypotheses. It recommends targeted logging and tests to verify the final fix.

Security Audit

Safe

v2 • 7/7/2026 Open versioned report

The static command findings are false positives caused by Markdown fences, inline examples, and non-executing debug snippets in SKILL.md. The two reconnaissance findings are ordinary debugging questions about timing and prevention, not system reconnaissance. No prompt injection, exfiltration intent, or hidden operational behavior was found.

Files scanned

231

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (16)

SKILL.md:72-78 SKILL.md:78-86 SKILL.md:86-95 SKILL.md:95-98 SKILL.md:98-104 SKILL.md:104-109 SKILL.md:109 SKILL.md:110 SKILL.md:132-160 SKILL.md:160-198 SKILL.md:198-210 SKILL.md:210-213 SKILL.md:213-215 SKILL.md:215-217 SKILL.md:217-220 SKILL.md:220-224

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/shubhamsaboo-debugger/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/shubhamsaboo-debugger/security.svg)](https://skillstore.io/skills/shubhamsaboo-debugger?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/shubhamsaboo-debugger?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shubhamsaboo-debugger/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/shubhamsaboo-debugger.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

shubhamsaboo. (2026). debugger security audit report (audit version 2) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/shubhamsaboo-debugger/audits/2

BibTeX citation

@techreport{shubhamsaboo-shubhamsaboo-debugger-2026,
  author = {shubhamsaboo},
  title = {debugger security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/shubhamsaboo-debugger/audits/2},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debugger security audit report (audit version 2)"
version: "1.0.0"
type: report
authors:
  - name: "shubhamsaboo"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/shubhamsaboo-debugger/audits/2"
identifiers:
  - type: other
    value: "skillstore:shubhamsaboo-debugger:audit:2"
    description: "Skillstore immutable audit report identifier"

Compare variants

3 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

shubhamsaboo Recommended Current

shubhamsaboo-debugger

Skillstore Score 80

Evidence Confidence Medium

Skillstore usage 6

Updated

2026-08-21

sickn33

sickn33-debugger

Skillstore Score 79

Evidence Confidence High

Skillstore usage 25

Updated

2026-08-21

cubha

cubha-debugger

Skillstore Score 69

Evidence Confidence Medium

Skillstore usage 4

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Investigate Application Errors

Turn stack traces, logs, and symptoms into prioritized causes and practical verification steps.

Triage Production Incidents

Organize intermittent failures by environment, timing, resource state, and likely contention points.

Review Regressions Before Release

Narrow a new failure to recent changes, missing tests, or dependency behavior before shipping.

Try These Prompts

Explain This Error

Debug this error. I will provide the message, stack trace, expected behavior, actual behavior, and recent changes. Ask only for missing details.

Find the Root Cause

Analyze these logs and symptoms. Give prioritized hypotheses, evidence for each one, and the next checks needed to confirm the root cause.

Design a Reproduction Plan

Create a minimal reproduction plan for this bug. Include required inputs, environment details, isolation steps, and observations that would confirm each hypothesis.

Debug a Production Incident

Help triage this production incident. Separate symptoms from causes, rank risks, propose safe diagnostics, define rollback signals, and recommend prevention steps.

Best Practices

Provide exact error text, stack traces, recent changes, and expected behavior before asking for a fix.
Validate each hypothesis with one small observation before changing code.
Add a regression test after the root cause is confirmed.

Avoid

Do not request broad rewrites before the failure mode is understood.
Do not hide logs, environment details, or reproduction steps that affect the analysis.
Do not treat symptoms as the root cause without supporting evidence.

Frequently Asked Questions

What problems does this skill help debug?

It helps with errors, crashes, regressions, intermittent failures, performance symptoms, and confusing application behavior.

Does it run commands automatically?

No. The skill provides investigation guidance. Any command execution depends on the host agent and user approval model.

Can it analyze stack traces?

Yes. It can explain stack traces, connect them to likely causes, and suggest targeted verification steps.

Can it fix the code directly?

It can recommend fixes. Direct edits require a compatible agent with file access, such as Codex or Claude Code.

What information should I provide?

Provide expected behavior, actual behavior, reproduction steps, logs, stack traces, environment details, and recent changes.

Is it suitable for production incidents?

Yes, for structured triage and diagnostics. Keep human incident owners responsible for customer impact and deployment decisions.

Developer Details

Author

shubhamsaboo

License

MIT

Author version

v1.0.0

Skillstore revision

Repository

https://github.com/shubhamsaboo/awesome-llm-apps/tree/main/awesome_agent_skills/debugger

Ref

412e23e39ccd9729546286287b96bb41707397cf

Maintenance freshness

7/18/2026

Usage

1 downloads · 1 views

File structure

📄 SKILL.md