Skills error-diagnostics-error-analysis
📦

error-diagnostics-error-analysis

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

Diagnose Errors and Resolve Incidents

Complex application failures are difficult to isolate across logs, traces, deployments, and services. This skill structures evidence, root-cause analysis, fixes, tests, and prevention.

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

Test it

Using "error-diagnostics-error-analysis". Checkout requests time out after a deployment, while database connection usage reaches its limit.

Expected outcome:

  • Impact: Checkout requests fail during peak traffic after the latest deployment.
  • Leading hypothesis: A query regression holds connections long enough to exhaust the pool.
  • Validation: Compare query duration by release and reproduce with production-like load.
  • Mitigation: Roll back the deployment, then verify error rate and pool recovery.
  • Prevention: Add query regression tests and alerts for pool saturation.

Using "error-diagnostics-error-analysis". A payment error appears intermittently across three services with different local timestamps.

Expected outcome:

  • Normalize all events to UTC and group them by correlation identifier.
  • Reconstruct the request path across the gateway, payment service, and provider.
  • Locate the first failing span and separate the originating error from downstream symptoms.
  • Test the leading timing hypothesis with controlled retries and tracing.

Using "error-diagnostics-error-analysis". Review error handling for a new API before production release.

Expected outcome:

  • Validate external inputs and return stable, non-sensitive error responses.
  • Add structured logs with request, trace, service, release, and error identifiers.
  • Define retry limits, circuit-breaker behavior, and graceful degradation.
  • Create alerts for error rate, latency, and new error fingerprints.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All 39 static alerts are false positives caused by inert Markdown examples, template literals, placeholder endpoints, or ordinary technical prose. The skill contains no executable scripts or automatic network, environment, or command access. No prompt injection or malicious intent 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-diagnostics-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-diagnostics-error-analysis/security.svg)](https://skillstore.io/skills/sickn33-error-diagnostics-error-analysis?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

BibTeX citation

@techreport{sickn33-sickn33-error-diagnostics-error-analysis-2026, author = {sickn33}, title = {error-diagnostics-error-analysis security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-error-diagnostics-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-diagnostics-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-diagnostics-error-analysis/audits/5" identifiers: - type: other value: "skillstore:sickn33-error-diagnostics-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

Investigate a Production Incident

Correlate symptoms, timelines, logs, traces, and deployments to identify a supported root-cause hypothesis.

Debug a Recurring Application Error

Narrow a failure, inspect its call path, and define focused tests for the proposed fix.

Improve Service Observability

Review error handling and recommend structured logs, correlation identifiers, tracing, monitoring, and alert thresholds.

Try These Prompts

Explain an Error 
Analyze this error message and stack trace: [details]. Explain the likely failure point, missing context, and three next checks.
Diagnose a Recurring Failure 
Investigate this recurring error using the supplied logs and reproduction steps: [details]. Rank hypotheses by evidence and propose targeted tests.
Analyze a Distributed Incident 
Build an incident timeline from these logs, traces, metrics, and deployments: [details]. Identify affected services, root cause, mitigation, and validation steps.
Design a Prevention Plan 
Review this completed incident analysis: [details]. Design code fixes, regression tests, observability improvements, alerts, rollback controls, and a reusable runbook.

Best Practices

  • Redact secrets and personal data before sharing diagnostics.
  • Separate observed evidence from hypotheses and state confidence clearly.
  • Validate fixes with focused tests, production-like conditions, monitoring, and rollback criteria.

Avoid

  • Do not change production systems without approval, safeguards, and a rollback plan.
  • Do not conclude root cause from one symptom or an isolated log line.
  • Do not add broad retries without limits, backoff, jitter, and error classification.

Frequently Asked Questions

What information should I provide?
Provide error messages, stack traces, timestamps, affected services, recent changes, reproduction steps, and relevant logs, metrics, or traces.
Can this skill debug distributed systems?
Yes. It can organize correlation identifiers, traces, dependencies, queue behavior, and timelines across services.
Does this skill make production changes?
It can propose changes, but production execution requires explicit approval, access controls, validation, and rollback planning.
Can it guarantee the root cause?
No. A root cause requires supporting evidence, hypothesis testing, and validation in the relevant environment.
Which observability tools does it support?
The playbook covers common patterns for Sentry, DataDog, OpenTelemetry, Prometheus, Grafana, Elasticsearch, Loki, Jaeger, and related tools.
How does it protect sensitive diagnostic data?
It directs users to redact secrets and personal data, and its examples demonstrate removal of cookies and authorization headers.

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-diagnostics-error-analysis

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

7 downloads · 112 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all