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 ./skills/error-debugging-error-trace/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

The body is well-organized into clear sections and keeps the overview lean, but it offers only high-level guidance with no executable specifics, and its single referenced resource file is missing from the bundle. Validation is mentioned but not built into an explicit feedback loop.

Suggestions

Add an explicit validation feedback loop (e.g. 'After deploying test errors, verify they are captured and grouped correctly; if not, adjust sampling/routing and re-test').

Provide at least one concrete, executable artifact in the body — a sample structured-logging snippet, a severity-level table, or an alert-routing config example — rather than only abstract steps.

Create the referenced 'resources/implementation-playbook.md' (or remove the dangling reference) so the progressive-disclosure navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned, but the opening paragraph duplicates the frontmatter description verbatim, so it could be tightened and not every token earns its place.	2 / 3
Actionability	It enumerates concrete steps ('Assess current error capture', 'Define severity levels', 'Validate signal quality with test errors') but provides no executable code, commands, tool names, or configuration examples, with detail offloaded to a referenced playbook.	2 / 3
Workflow Clarity	A clear assess→define→configure→validate sequence is present with a validation mention, but there are no explicit checkpoints or a validate→fix→retry feedback loop.	2 / 3
Progressive Disclosure	The overview is clean and points one level deep to a clearly signaled 'resources/implementation-playbook.md', but that referenced file does not exist in the bundle, so navigation is broken rather than easy.	2 / 3
	Total	8 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 clearly conveys the skill's domain and lists concrete capabilities, but it relies on second-person voice and omits an explicit 'Use when…' trigger clause, capping completeness and trigger quality. It is competent but generic rather than sharply distinctive.

Suggestions

Rewrite in third person and add an explicit trigger clause, e.g. 'Use when setting up error monitoring, configuring alerts, or implementing structured logging and tracing.'

Include common natural variations and tool names users would actually say (e.g. Sentry, Datadog, Rollbar, alert routing) to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions ('Set up error tracking systems, configure alerts, implement structured logging'), which would merit a 3, but the second-person opener 'You are an error tracking and observability expert' triggers the rubric's voice penalty, reducing it to 2.	2 / 3
Completeness	It clearly answers what the skill does, but provides no explicit when/trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Relevant natural terms appear ('error tracking', 'monitoring', 'alerts', 'structured logging', 'production issues'), but there is no 'Use when…' clause and common variations such as specific tool names (Sentry, Datadog) are missing.	2 / 3
Distinctiveness Conflict Risk	The error-tracking/observability niche is reasonably specific, but the absence of explicit triggers means it could still overlap with general logging, monitoring, or DevOps skills.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/error-debugging-error-trace/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.