Error debugging error trace

Skill AravindS-Wick/aravindhan-skills/skills/library/error-debugging-error-trace

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.From its SKILL.md

Install

npx -y skills add AravindS-Wick/aravindhan-skills --skill error-debugging-error-trace

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 269 tokens by cl100k_base, as published. Nobody here has run it

Error Tracking and Monitoring

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.md for detailed monitoring patterns and examples.

What ships with it: 1 file

41.7 KB alongside SKILL.md

resources/

implementation-playbook.md41.7 KB

Gives 0 of the 12 instructions most monitoring observability skills give in 269 tokens

Counted across 530 of the 532 authors here whose files we hold, read 2026-09-06

Use structured JSON loggingin 40 of 530, across 36 files
Link every alert to a runbookin 29 of 530, across 27 files
Attach correlation IDs to every log linein 19 of 530, across 16 files
Alert on symptoms rather than causesin 19 of 530, across 17 files
Use OpenTelemetry for distributed tracingin 15 of 530, across 14 files
Alert on symptoms users feelin 15 of 530, across 13 files
Implement health check endpointsin 14 of 530, across 10 files
Inspect existing dashboards firstin 12 of 530, across 4 files
Build the minimum useful boardin 12 of 530, across 4 files
Start from operator questionsin 12 of 530, across 4 files
Propagate trace context across boundariesin 11 of 530, across 10 files
Include trace id in all log entriesin 10 of 530, across 9 files

Said here and by no other author read

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

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.