# 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.

## Install

```bash
npx skillstore add sickn33/error-diagnostics-error-trace
```

## Metadata

- Status: approved
- Slug: sickn33-error-diagnostics-error-trace
- Skillstore revision: r2
- Version status: missing
- Tree hash: 0f55898048a2fe13faa2512d5a67b2f0538e51735ff8d415c03b6d93b19abd3a
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-diagnostics-error-trace
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-error-diagnostics-error-trace
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-error-diagnostics-error-trace/manifest

## Capabilities

- Assess existing error handling, logging frameworks, monitoring coverage, and common failure patterns.
- Plan integrations with error tracking services and custom event reporting endpoints.
- Design structured logs with severity levels, metadata, redaction, rotation, and production transports.
- Define alert rules, error grouping, deduplication, performance metrics, and recovery strategies.
- Outline real-time dashboards for error rates, affected users, trends, recent events, and active alerts.

## Use Cases

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

## Prompt Templates

### 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.
```

## Limitations

- The skill provides guidance and examples but does not deploy or operate monitoring services.
- Generated configurations require testing against the selected platform, runtime, and data protection rules.
- Examples cover common patterns and may require adaptation for unsupported languages or vendors.
- The skill cannot diagnose production incidents without relevant logs, traces, code, and system context.

## 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.

## Anti Patterns

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

## Security Audit

- Audited at: 2026-07-23T23:51:40.501\+00:00
- Summary: 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.

## Stats

- Views: 108
- Downloads: 10
- Favorites: 0
- Popularity score: 0