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.
SkillScore74Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/29/2026
What it changes
Passed 17 of 23 test cases with the skill, and 14 of 23 without it.
Without skill61%
With skill74%
Checks it passed that the model alone missed
The response specifies filtering out sensitive payment details and PII prior to log ingestion.
The response includes steps to fire test errors containing mock sensitive data to verify redaction.
The response instructs verifying that generated test errors route to the intended alerting destinations.
and 1 more in the full report
4 fixed13 passed either way5 still failing1 broke
Pass-rate lift
+13 pp
Tokens
+8%
Agent turns
0%
Response time
0%
Model gemini-3.6-flashMeasured 8/29/2026v117 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
Our high-throughput Go payment service handles 50,000 requests per second. Developers want to log every single stack trace in production to ensure total visibility. How should we configure our logging architecture to maintain visibility without crashing our log store?
What was checked, without and with the skill
Checked
Without skill
With skill
The response recommends implementing dynamic or tail-based log sampling to prevent system overload.
Passed
Passed
The response specifies filtering out sensitive payment details and PII prior to log ingestion.
Missed
Passed
case-08 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md43 linessingle file
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.md for detailed monitoring patterns and examples.