error-diagnostics-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,

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

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

Quality

Content

38%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 content is a generic template that restates the description, offers only vague platitudes instead of executable guidance, and relies on a referenced playbook file that is missing from the bundle.

Suggestions

Replace generic Instructions with concrete, executable guidance: example alert-rule configs, structured-logging snippets, and integration setup commands for common services (Sentry, Datadog).

Add explicit validation checkpoints to the workflow (e.g., trigger a test error and confirm it appears in the dashboard before finalizing alert rules).

Either provide the referenced `resources/implementation-playbook.md` file or remove the broken reference so progressive disclosure navigation actually works.

Dimension	Reasoning	Score
Conciseness	The body is short and sectioned but restates the frontmatter description verbatim ("You are an error tracking and observability expert...") and includes generic filler sections (Use/Do not use/Context) that could be tightened.	3 / 5
Actionability	Only high-level hints are given ("Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") with no code, commands, configs, or concrete examples; the single detailed reference points to a non-existent file.	2 / 5
Workflow Clarity	A rough sequence exists via the eight-item Output Format list and a generic "validate outcomes" instruction, but there are no concrete validation checkpoints or feedback loops for configuration work.	3 / 5
Progressive Disclosure	The body is organized into sections and signals one-level-deep references to `resources/implementation-playbook.md`, but that file does not exist in the bundle, so navigation is broken.	2 / 5
	Total	10 / 20 Passed

Description

61%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 names a clear domain and several concrete actions but is cut off mid-sentence, omits any "Use when" trigger guidance, and uses penalized second-person voice, capping completeness and specificity.

Suggestions

Complete the truncated sentence and convert to third-person voice (e.g., "Sets up error tracking systems, configures alerts, and implements structured logging...").

Add an explicit "Use when..." clause naming concrete trigger phrases (e.g., error tracking, Sentry/Datadog setup, alert configuration, production error monitoring).

Include natural synonyms and named services users would say (e.g., "error reporting", "Sentry", "Datadog", "Rollbar") to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ("Set up error tracking systems, configure alerts, implement structured logging") which would rate a 4, but the description uses second-person voice ("You are an error tracking and observability expert") and is cut off mid-sentence, reducing specificity by one per the voice penalty.	3 / 5
Completeness	It states a clear "what" but has no "Use when..." clause or equivalent trigger guidance, capping completeness at 3; the sentence is also truncated, further weakening the "what".	3 / 5
Trigger Term Quality	Good natural keyword coverage ("error tracking", "observability", "error monitoring", "alerts", "structured logging") that users would plausibly say, though synonyms like "error reporting", "logging services", or named tools (Sentry) are missing.	4 / 5
Distinctiveness Conflict Risk	The error-tracking/observability niche is mostly distinct with specific triggers, with only minor overlap risk against broad monitoring or logging skills.	4 / 5
	Total	14 / 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-diagnostics-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.