Skills debugger
📦

debugger

Content revision r2 Safe ⚙️ External commands

Diagnose Software Failures Systematically

Software failures can hide behind incomplete logs and unclear reproduction steps. This skill structures investigation, isolates root causes, proposes minimal fixes, and defines verification.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

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/sickn33-debugger.md and its manifest at https://skillstore.io/api/skills/sickn33-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/sickn33-debugger.md Signed manifest GET /api/skills/sickn33-debugger/manifest Signed lockfile GET /api/skills/sickn33-debugger/lockfile

Test it

Using "debugger". A checkout test starts timing out after a client dependency update.

Expected outcome:

  • Root cause: The updated client waits for a callback that the test double never invokes.
  • Evidence: The failure begins after the update and stops at the callback wait.
  • Fix: Update the test double to match the current callback behavior.
  • Verification: Repeat the targeted test, then run the related checkout suite.

Using "debugger". A production service returns occasional unauthorized responses after token refresh.

Expected outcome:

  • Leading hypothesis: Concurrent requests reuse an expired token during refresh.
  • Evidence needed: Compare token timestamps, refresh events, and request identifiers.
  • Isolation plan: Add focused logging around token selection and refresh completion.
  • Verification: Reproduce concurrent requests and confirm every request uses the refreshed token.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

The only static finding is a false positive caused by an inline Markdown path at SKILL.md line 28. The prompt-only skill contains no executable command or harmful intent.

1
Files scanned
59
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
SKILL.md:28
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
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-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

sickn33. (2026). debugger security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-debugger/audits/5

BibTeX citation

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

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 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-debugger/audits/5" identifiers: - type: other value: "skillstore:sickn33-debugger:audit:5" 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
shubhamsaboo Recommended

shubhamsaboo-debugger

Skillstore Score 80
Evidence Confidence Medium
Skillstore usage 6
Updated

2026-08-21

sickn33 Current

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: High
55
Architecture
85
Maintainability
87
Content
68
Community
91
Spec Compliance

What You Can Build

Resolve Application Errors

Trace an exception from its stack trace and recent changes, then define a focused fix and regression test.

Investigate Failing Tests

Separate test defects from product defects by reproducing failures and checking assumptions, fixtures, and environment differences.

Diagnose Production Incidents

Use logs and observed symptoms to rank hypotheses, isolate affected components, and plan safe verification.

Try These Prompts

Triage an Error 
Analyze this error message: [error]. Ask for missing context, identify likely failure areas, and give the first three checks.
Diagnose a Failing Test 
Investigate this failing test using [test output] and [recent changes]. Define reproduction steps, rank hypotheses, and suggest evidence for each.
Isolate an Intermittent Defect 
Create an isolation plan for this intermittent failure: [symptoms]. Include targeted logging, variable states, controlled experiments, and success criteria.
Complete a Root Cause Analysis 
Analyze [stack trace], [logs], [reproduction], and [diff]. Explain the root cause, propose the smallest fix, and define verification and prevention measures.

Best Practices

  • Provide the complete error, stack trace, reproduction steps, and recent relevant changes.
  • Test one hypothesis at a time and record evidence that confirms or rejects it.
  • Verify the fix with a targeted regression test and related test coverage.

Avoid

  • Do not change several components before identifying the failure location.
  • Do not suppress errors or symptoms without explaining the underlying cause.
  • Do not accept a fix until the original failure is reproducible and verified.

Frequently Asked Questions

What information should I provide first?
Provide the full error, stack trace, reproduction steps, expected behavior, actual behavior, environment details, and recent changes.
Can this skill debug intermittent failures?
Yes. It can design logging and controlled experiments, but intermittent issues require enough observations to compare successful and failed runs.
Will it modify my code automatically?
It can propose or implement a focused fix when tools and permissions allow. You should still review and test every change.
Can it diagnose production incidents?
Yes, when you provide relevant logs, symptoms, timelines, and constraints. Validate all recommendations through your incident procedures.
How does it verify a root cause?
It links the diagnosis to evidence, tests competing hypotheses, reproduces the failure, and confirms that a focused change removes it.
When should I use another skill?
Use another skill when the task primarily requires security analysis, architecture design, deployment operations, or specialized domain knowledge.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/debugger

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

23 downloads · 88 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all