Automated summary
This skill guides the setup of production error monitoring, covering error capture, grouping, alerting, and structured logging.
Strengths
- Covers the full chain: error capture, grouping, severity levels, and alert routing
- Includes a validation step using test errors to check signal quality
- Explicitly warns against logging secrets, tokens, and personal data
- Provides a detailed implementation playbook as a resource for advanced workflows
Limitations
- Assumes runtime and monitoring platform access, otherwise not applicable
- Does not address one-off bug fixing for an isolated issue
- The SKILL.md body does not include vendor-specific configuration details
Use it when setting up or improving production error observability with alerts and structured logs.
Avoid it when the system has no runtime or monitoring access, or when the task is just fixing a single bug.
Security analysis
SafeThe skill contains only high-level observability guidance and explicitly warns against logging secrets, tokens, or personal data. It includes no executable commands, network calls, credential access, destructive operations, or hidden payloads.
No concerns found
How this analysis is madeExamples
Our Node.js API has no error monitoring. Help me set up error tracking with severity levels, alert routing, and structured logging.Our error alerts are noisy and everyone ignores them. Help me define grouping rules and a triage workflow.Review our current Sentry setup and validate the signal quality by generating test errors across our services.name: error-debugging-error-trace description: "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi..." risk: unknown source: community
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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/error-tracking-and-monitoring-mrx3xyq3/download' --output '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md.part' && mv '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md.part' '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
$ARGUMENTS
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md' && test -s '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/error-debugging-error-trace' && cp -R '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3' '.claude/skills/error-debugging-error-trace'Cursor
test -f '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md' && test -s '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/error-debugging-error-trace' && cp -R '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3' '.cursor/skills/error-debugging-error-trace'Codex
test -f '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md' && test -s '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/error-debugging-error-trace' && cp -R '.skill-downloads/error-tracking-and-monitoring-mrx3xyq3' '.agents/skills/error-debugging-error-trace'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/error-tracking-and-monitoring-mrx3xyq3'openskills read 'error-tracking-and-monitoring-mrx3xyq3'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/error-tracking-and-monitoring-mrx3xyq3/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.