Skills error-debugging-error-trace
📦

error-debugging-error-trace

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

Build Reliable Error Tracking and Monitoring

Production errors are difficult to diagnose when telemetry and alerts are inconsistent. This skill designs practical monitoring, logging, grouping, recovery, and dashboard workflows.

Supports: Claude Codex Code(CC)
📊 70 Adequate

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

Test it

Using "error-debugging-error-trace". Assess error monitoring for a Node.js API with console logs and no centralized tracker.

Expected outcome:

  • Current state: exceptions and request failures are difficult to correlate across instances.
  • Priority: add structured fields, centralized capture, and a release identifier.
  • Validation: emit controlled test errors and confirm grouping, redaction, and alert delivery.

Using "error-debugging-error-trace". Design alerts for a payment service with a one percent error budget.

Expected outcome:

  • Critical: page when the fast error-budget burn exceeds the agreed threshold.
  • Warning: notify the service channel for sustained latency or error increases.
  • Controls: add cooldowns, ownership, runbook links, and recovery notifications.

Using "error-debugging-error-trace". Create a plan to reduce duplicate database error reports.

Expected outcome:

  • Normalize request identifiers, timestamps, memory addresses, and dynamic file paths.
  • Fingerprint by error type, normalized message, stable code location, and database error code.
  • Test grouping against representative incidents before changing production behavior.

Security Audit

Medium Risk
v5 • 7/23/2026 Open versioned report

All 15 static findings are false positives involving template literals, Markdown code spans, defensive redaction keys, and expected observability network examples. A medium privacy concern remains because examples can export user context or log identifiers and full URLs without complete redaction.

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

Confirmed security concerns (1)

Medium
resources/implementation-playbook.md:179-187resources/implementation-playbook.md:228-230resources/implementation-playbook.md:552-558
Potential Personal Data Logging and Telemetry
Examples attach user identifiers and arbitrary user context to telemetry, then log client IP addresses and full request URLs. These fields can expose personal data or query secrets.
The examples explicitly attach user data to events and log IP addresses and full URLs. The shown controls do not fully redact these fields.

Risk Factors

⚙️ External commands (7)
resources/implementation-playbook.md:409-415 resources/implementation-playbook.md:415-419 resources/implementation-playbook.md:484-531 resources/implementation-playbook.md:531-575 resources/implementation-playbook.md:1240-1348 SKILL.md:37 SKILL.md:46
🌐 Network access (2)
resources/implementation-playbook.md:405 resources/implementation-playbook.md:1323
🔑 Env variables (3)
resources/implementation-playbook.md:228 resources/implementation-playbook.md:229 resources/implementation-playbook.md:364
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-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-debugging-error-trace/security.svg)](https://skillstore.io/skills/sickn33-error-debugging-error-trace?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

BibTeX citation

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

Skillstore Score

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

What You Can Build

Improve Service Error Capture

Assess exception handling and add structured, privacy-aware error reporting to a service.

Reduce Alert Noise

Design severity thresholds, cooldowns, alert channels, and triage workflows for production incidents.

Standardize Observability

Create shared grouping, performance, recovery, and dashboard patterns for multiple services.

Try These Prompts

Assess Error Monitoring 
Review this service structure and current error handling. Identify monitoring gaps, privacy risks, and the three highest priority improvements.
Design Structured Logging 
Design structured logging for this application. Define fields, levels, redaction rules, retention needs, and transports for development and production.
Create Alerting and Triage 
Create alert rules for these service objectives and metrics. Include thresholds, windows, cooldowns, routing, ownership, and validation tests.
Plan an Observability System 
Design an end-to-end error monitoring system for this architecture. Cover capture, grouping, tracing, alerts, recovery, dashboards, privacy, rollout, and verification.

Best Practices

  • Start with service objectives, failure modes, data sensitivity, and incident ownership.
  • Redact sensitive fields before export and validate controls with representative test events.
  • Tune grouping and alerts using production evidence, then document thresholds and runbooks.

Avoid

  • Do not send request bodies, credentials, or personal data to telemetry by default.
  • Do not page on every exception without thresholds, grouping, and cooldowns.
  • Do not deploy reference examples without dependency, privacy, load, and failure testing.

Frequently Asked Questions

Does this skill require a specific monitoring provider?
No. It includes provider-specific and custom patterns that must be adapted to your environment.
Can it configure Sentry?
It can design Sentry setup, filtering, sampling, fingerprinting, and middleware patterns. You must provide project details and credentials through approved channels.
Will it access production systems automatically?
No. Runtime, repository, and monitoring access depend on the tools and permissions available in your session.
How does it protect sensitive data?
It recommends redaction and filtering. You must verify field coverage, privacy requirements, retention, and provider settings before deployment.
Can it reduce duplicate alerts?
Yes. It provides fingerprinting, normalization, grouping, thresholds, and cooldown patterns that require tuning with representative incidents.
Are the implementation examples production ready?
No. They are reference patterns and require adaptation, dependency checks, testing, security review, and operational validation.

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-trace

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

7 downloads · 127 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all