Skills error-debugging-error-analysis
📦

error-debugging-error-analysis

Content revision r2 Safe ⚡ Contains scripts⚙️ External commands🌐 Network access🔑 Env variables

Diagnose Errors and Resolve Production Incidents

Complex failures can hide across logs, traces, services, and recent changes. This skill structures evidence, tests hypotheses, and recommends fixes with prevention steps.

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

Test it

Using "error-debugging-error-analysis". A payment request times out after 30 seconds, and the trace ends at the database client.

Expected outcome:

  • Likely cause: database pool exhaustion or a slow query on the payment path.
  • Evidence needed: pool metrics, query duration, lock waits, and deployment changes.
  • Next step: reproduce safely with tracing and compare healthy requests.

Using "error-debugging-error-analysis". Error rates rose after version 2.3.1, but only one service shows new exceptions.

Expected outcome:

The deployment is the leading hypothesis. Compare changed code paths, correlate exception timestamps, and test rollback or feature-flag mitigation.

Using "error-debugging-error-analysis". Several services report failures for requests sharing the same correlation identifier.

Expected outcome:

Build a timestamped request path across services. Locate the first failed span, then distinguish the originating failure from downstream symptoms.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All 39 static findings are false positives caused by fenced examples, template literals, reserved addresses, prose, or Markdown. The files contain debugging guidance and safety cautions; no executable payload, prompt injection, credential collection, or covert network behavior was found.

2
Files scanned
1,200
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚡ Contains scripts (1)
resources/implementation-playbook.md:850-858
⚙️ External commands (4)
resources/implementation-playbook.md:420-430 resources/implementation-playbook.md:692-712 SKILL.md:41 SKILL.md:50
🌐 Network access (7)
resources/implementation-playbook.md:703 resources/implementation-playbook.md:229 resources/implementation-playbook.md:703 resources/implementation-playbook.md:946 resources/implementation-playbook.md:984 resources/implementation-playbook.md:1102 resources/implementation-playbook.md:177
🔑 Env variables (10)
resources/implementation-playbook.md:734 resources/implementation-playbook.md:735 resources/implementation-playbook.md:736 resources/implementation-playbook.md:758 resources/implementation-playbook.md:759 resources/implementation-playbook.md:734 resources/implementation-playbook.md:735 resources/implementation-playbook.md:736 resources/implementation-playbook.md:758 resources/implementation-playbook.md:759
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-error-debugging-error-analysis/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-error-debugging-error-analysis.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). error-debugging-error-analysis security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-error-debugging-error-analysis/audits/5

BibTeX citation

@techreport{sickn33-sickn33-error-debugging-error-analysis-2026, author = {sickn33}, title = {error-debugging-error-analysis security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-error-debugging-error-analysis/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: "error-debugging-error-analysis security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-error-debugging-error-analysis/audits/5" identifiers: - type: other value: "skillstore:sickn33-error-debugging-error-analysis:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Debug an Application Failure

Analyze an exception and stack trace, isolate the failing path, and define focused verification steps.

Investigate a Production Incident

Correlate logs, traces, deployments, and service dependencies to build a timeline and identify likely root causes.

Prevent Recurring Errors

Turn incident evidence into corrective actions for tests, monitoring, alerting, ownership, and rollback readiness.

Try These Prompts

Explain an Error 
Analyze this error message and stack trace: [details]. Identify the likely cause, explain the evidence, and suggest safe verification steps.
Investigate a Recurring Failure 
Investigate this recurring failure using these logs and timestamps: [details]. Group patterns, rank hypotheses, and propose targeted experiments.
Trace a Distributed Incident 
Analyze this cross-service incident using logs, traces, deployment history, and service dependencies: [details]. Build a timeline and identify the root cause.
Design a Prevention Plan 
Review this resolved incident: [details]. Create corrective actions covering code fixes, tests, observability, alerting, rollback readiness, and ownership.

Best Practices

  • Provide exact timestamps, versions, error messages, and affected services.
  • Separate observed evidence from assumptions and test each hypothesis.
  • Redact secrets and personal data before sharing logs or traces.

Avoid

  • Do not change production systems without approval and a rollback plan.
  • Do not treat the final stack frame as the root cause without tracing inputs.
  • Do not add broad retries without checking idempotency and retryable failures.

Frequently Asked Questions

What information should I provide?
Provide the error message, stack trace, timestamps, affected services, recent changes, and relevant logs or traces.
Can this skill diagnose intermittent failures?
Yes. It can compare timing, load, environment, and correlation patterns when enough observations are available.
Does this skill make production changes?
No. It recommends safe experiments and fixes, but production changes require explicit approval, testing, and rollback planning.
Can it analyze distributed systems?
Yes. It can correlate service dependencies, trace identifiers, queues, deployments, and cascading failures.
Which observability tools are supported?
The playbook includes general patterns and examples for Sentry, DataDog, OpenTelemetry, Prometheus, Grafana, and related tools.
How should sensitive diagnostic data be handled?
Remove credentials, authorization headers, cookies, personal data, and unnecessary payloads before sharing diagnostic material.

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/error-debugging-error-analysis

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

9 downloads · 127 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all