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.

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/error-debugging-error-trace/SKILL.md

The canonical home for this skill is error-debugging-error-trace in rmyndharis/antigravity-skills

Quality

Content

46%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is concise and well-sectioned but offers only abstract, tool-agnostic guidance with no executable specifics, and its single progressive-disclosure reference points to a file that is absent from the bundle.

Suggestions

Add concrete, actionable guidance: name specific services/SDKs (Sentry, Datadog, OpenTelemetry) with example config snippets or commands for the common cases.

Create the referenced 'resources/implementation-playbook.md' file (or fix the path) so the progressive-disclosure pointer resolves to real content.

Tighten the workflow with explicit validation checkpoints (e.g., 'emit a test error and confirm it is grouped and alerted before rolling out') to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no concept over-explanation, but the opening paragraph restates the frontmatter description verbatim, a minor redundancy that keeps it just below the lean-and-perfect anchor.	4 / 5
Actionability	Instructions are high-level directives ('Assess current error capture', 'Define severity levels', 'Configure logging, tracing, and alert routing') with no concrete tools, commands, or specific steps to execute.	2 / 5
Workflow Clarity	A rough sequence exists (Assess, Define, Configure, Validate) with one validation step ('Validate signal quality with test errors'), but checkpoints are otherwise implicit and steps lack concrete detail.	3 / 5
Progressive Disclosure	The body references 'resources/implementation-playbook.md' twice, but that file and directory do not exist in the bundle, so the signaled reference is a broken pointer with no navigable detail.	2 / 5
	Total	11 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states concrete capabilities but omits any explicit 'Use when...' trigger clause, capping completeness, and its second-person voice costs specificity. It is reasonably distinctive but reads more as a persona statement than a trigger-rich skill description.

Suggestions

Rewrite in third person and add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when setting up Sentry/Datadog, configuring error alerts, or structuring production logging').

Replace generic actions with tool-specific ones (e.g., 'configure Sentry release tracking', 'set up Datadog APM error rates') to lift specificity toward 5.

Add user-natural synonyms and file/term variants (e.g., 'error monitoring, observability, alerting, on-call triage') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several actions ('Set up error tracking systems, configure alerts, implement structured logging') but they remain high-level with no specific tools, and the second-person 'You are an error tracking... expert' voice triggers the -1 specificity penalty from the rubric.	3 / 5
Completeness	Provides a clear 'what' via four capability actions but includes no 'Use when...' or equivalent explicit trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Contains relevant domain keywords ('error tracking', 'observability', 'error monitoring', 'alerts', 'structured logging') but lacks common synonyms and natural user variations, sitting at the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'error tracking and observability' niche is mostly distinct with only minor overlap risk against closely related logging or general monitoring skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/error-debugging-error-trace/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.