Skills error-diagnostics-error-trace

📦

error-diagnostics-error-trace

Name: error-diagnostics-error-trace
Author: sickn33

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

Build Reliable Error Monitoring

Production errors are difficult to resolve without consistent telemetry and actionable alerts. This skill creates structured plans for tracking, grouping, reporting, and recovering from failures.

Supports: Claude Codex Code(CC)

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

Test it

Using "error-diagnostics-error-trace". Assess error monitoring for a Node.js API that only writes console errors.

Expected outcome:

The assessment identifies missing structured context, centralized reporting, request correlation, and alert ownership. It prioritizes capture middleware, redaction, and deployment verification.

Using "error-diagnostics-error-trace". Create alert rules for a payment service with repeated timeout errors.

Expected outcome:

The plan groups timeouts by dependency and operation, defines rate and impact thresholds, limits duplicate notifications, and includes recovery alerts.

Using "error-diagnostics-error-trace". Plan an error dashboard for several production services.

Expected outcome:

The dashboard includes error rate, affected users, top groups, service trends, recent events, active alerts, and mean recovery time.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 13 static findings are false positives caused by documentation examples, JavaScript template literals, Markdown code spans, or benign observability integrations. No executable shell commands, environment-secret reads, reconnaissance behavior, unauthorized network activity, or prompt injection was found.

Files scanned

1,429

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (7)

resources/implementation-playbook.md:419-425 resources/implementation-playbook.md:425-429 resources/implementation-playbook.md:494-541 resources/implementation-playbook.md:541-585 resources/implementation-playbook.md:1250-1358 SKILL.md:34 SKILL.md:51

🌐 Network access (2)

resources/implementation-playbook.md:415 resources/implementation-playbook.md:1333

🔑 Env variables (3)

resources/implementation-playbook.md:238 resources/implementation-playbook.md:239 resources/implementation-playbook.md:374

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/sickn33-error-diagnostics-error-trace/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-trace/security.svg)](https://skillstore.io/skills/sickn33-error-diagnostics-error-trace?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

BibTeX citation

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

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Establish Error Tracking

Create an implementation plan for event capture, sensitive-data redaction, service integration, and deployment validation.

Improve Incident Alerts

Design grouped alerts with thresholds, escalation routes, rate limits, and actionable diagnostic context.

Standardize Observability

Define shared logging fields, dashboard metrics, recovery policies, and troubleshooting documentation across services.

Try These Prompts

Review Error Handling

Review this application error handling approach. Identify missing capture points, weak context, and the three highest-priority improvements.

Plan Service Integration

Create an error tracking integration plan for [runtime] using [service]. Include configuration, redaction, sampling, release tracking, and validation.

Design Alerts and Grouping

Design alert and grouping rules for [system]. Address fingerprints, severity, thresholds, escalation, duplicate suppression, and recovery notifications.

Build an Observability Architecture

Design production error observability for [architecture]. Cover collection, structured logs, privacy controls, performance impact, dashboards, resilience, and rollout verification.

Best Practices

Provide the runtime, deployment model, monitoring vendor, traffic profile, and data sensitivity before requesting implementation guidance.
Redact credentials and personal data before sharing logs or sending events to any monitoring service.
Test capture, grouping, alert delivery, performance overhead, and recovery behavior in a controlled environment before production rollout.

Avoid

Do not send complete request bodies, credentials, or personal data to error tracking systems.
Do not alert on every event without grouping, thresholds, ownership, and escalation rules.
Do not deploy generated examples without adapting dependencies, security controls, and failure handling to the target environment.

Frequently Asked Questions

Does this skill support a specific monitoring vendor?

It provides vendor-neutral guidance and examples for common services, including Sentry-style and custom reporting integrations.

Can it analyze my existing error handling?

Yes. Provide relevant code, logging configuration, architecture details, and expected failure scenarios.

Does it automatically access production logs?

No. It only uses context and files supplied through the active coding environment.

How does it protect sensitive information?

It recommends explicit redaction, restricted event context, controlled destinations, and validation against applicable privacy requirements.

Can it create alerting and dashboard plans?

Yes. It can define metrics, grouping, thresholds, escalation paths, real-time views, and validation steps.

Is generated configuration ready for production?

No. Review and test every configuration against your runtime, vendor, security controls, traffic, and operational procedures.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-diagnostics-error-trace

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

8 downloads · 108 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md