error-debugging-error-trace
Implements comprehensive error monitoring and logging systems to help teams identify and fix production issues.
Install
mkdir -p .claude/skills/error-debugging-error-trace && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4161" && unzip -o skill.zip -d .claude/skills/error-debugging-error-trace && rm skill.zipInstalls to .claude/skills/error-debugging-error-trace
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.Key capabilities
- →Set up error tracking systems
- →Configure alert routing
- →Implement structured logging
- →Define severity thresholds
How it works
The skill assesses current error capture and configures structured logging, tracing, and alerting logic.
Inputs & outputs
When to use error-debugging-error-trace
- →Setup production error tracking systems
- →Define alert routing and severity thresholds
- →Implement structured logging practices
- →Configure error grouping and triage workflows
About this skill
Error Tracking and Monitoring
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.
Use this skill when
- Implementing or improving error monitoring
- Configuring alerts, grouping, and triage workflows
- Setting up structured logging and tracing
Do not use this skill when
- The system has no runtime or monitoring access
- The task is unrelated to observability or reliability
- You only need a one-off bug fix
Context
The user needs to implement or improve error tracking and monitoring. Focus on real-time error detection, meaningful alerts, error grouping, performance monitoring, and integration with popular error tracking services.
Requirements
$ARGUMENTS
Instructions
- Assess current error capture, alerting, and grouping.
- Define severity levels and triage workflows.
- Configure logging, tracing, and alert routing.
- Validate signal quality with test errors.
- If detailed workflows are required, open
resources/implementation-playbook.md.
Safety
- Avoid logging secrets, tokens, or personal data.
- Use safe sampling to prevent overload in production.
Resources
resources/implementation-playbook.mdfor detailed monitoring patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
When not to use it
- →Systems without runtime access
- →One-off bug fixes
Prerequisites
Limitations
- →Requires system access
- →Avoid logging secrets or personal data
How it compares
It provides a complete observability setup rather than just basic error logging.
Compared to similar skills
error-debugging-error-trace side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| error-debugging-error-trace (this skill) | 1 | 4mo | No flags | Intermediate |
| gcloud-usage | 1 | 8mo | No flags | Intermediate |
| error-diagnostics-error-trace | 1 | 4mo | No flags | Intermediate |
| devops-troubleshooter | 1 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
gcloud-usage
fcakyon
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
error-diagnostics-error-trace
sickn33
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,
devops-troubleshooter
sickn33
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use PROACTIVELY for debugging, incident response, or system troubleshooting.
autotel
jagreehal
Use when instrumenting with trace/span/track, reviewing code for logging and observability patterns, converting console.log to wide events, adding structured errors, setting up canonical log lines, configuring init(), adding subscribers, or working in the autotel monorepo.
ai-debug-harness
DeandreFu
Self-driving Electron + Node debug harness with NDJSON logs, Playwright E2E, doctor preflight, and a YAML-frontmatter cookbook of known causes. Use when a voice-chat E2E flow misbehaves locally, audio publish silently fails, the agent worker emits warnings, or any LiveKit/Electron/Fastify error appe
analyze-prod-issue
MaxPayne89
>-