error-diagnostics-error-analysis

You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.

Quality

30%

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

Quality

Content

36%Scale 1-5

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

This skill provides a high-level framework for error analysis but lacks the concrete, actionable guidance needed to be truly useful. The instructions read as abstract process descriptions rather than executable steps with specific tools, commands, or examples. The referenced playbook file doesn't exist in the bundle, undermining the progressive disclosure strategy.

Suggestions

Add concrete, executable examples: specific commands for log analysis (e.g., grep patterns, jq queries), distributed tracing tool usage, or structured debugging scripts that Claude can actually run.

Include validation checkpoints in the workflow, such as 'Confirm root cause by reproducing the error with X isolated' or 'Verify fix by checking error rate drops below threshold Y'.

Provide the referenced `resources/implementation-playbook.md` file or remove the reference and inline the most critical checklist items directly in the Instructions section.

Replace vague instructions like 'Gather error context' with specific steps like 'Read the error log file, extract the stack trace, identify the failing service and timestamp, and check for correlated errors within a 5-minute window'.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanation (the Context section largely restates what Claude already knows about error analysis) and the 'Use this skill when' / 'Do not use this skill when' sections add moderate padding. The Instructions section is reasonably lean but the overall content could be tightened.	3 / 5
Actionability	The instructions are high-level and vague ('Gather error context', 'Reproduce or narrow the issue', 'Identify root cause'). There are no concrete commands, code examples, specific tool invocations, or executable steps. It reads more like abstract guidance than actionable instructions.	2 / 5
Workflow Clarity	There is a rough sequence (gather → reproduce → identify → propose), but steps are poorly defined with no specifics on how to execute them. There are no validation checkpoints, no feedback loops for when diagnosis fails, and no concrete verification steps. For a skill involving production incident analysis (potentially destructive operations), this lack of validation is significant.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed frameworks, which is a reasonable one-level-deep reference. However, no bundle files are provided, so the referenced file doesn't exist. The main content is appropriately brief but the reference is unverifiable and the structure is minimal.	3 / 5
	Total	10 / 20 Passed

Description

23%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.

This description reads as a persona/role definition ('You are an expert...') rather than a functional skill description. It uses first/second person framing, lacks concrete actions, provides no 'when to use' guidance, and covers an overly broad domain without clear boundaries. It would perform poorly in a multi-skill selection scenario.

Suggestions

Replace the persona framing with third-person action statements listing concrete capabilities, e.g., 'Analyzes error logs and stack traces, diagnoses production incidents in distributed systems, designs monitoring dashboards and alerting rules.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions error logs, stack traces, production outages, monitoring setup, distributed tracing, or observability pipelines.'

Narrow the scope or clearly delineate sub-capabilities to reduce overlap risk with other debugging or monitoring skills.

Dimension	Reasoning	Score
Specificity	Names the domain (debugging distributed systems, production incidents, observability) but provides no concrete actions. 'Analyzing', 'debugging', and 'implementing' are generic verbs without specific deliverables or outputs.	2 / 5
Completeness	There is only a vague 'what' (expertise in debugging/analyzing/implementing) and no 'when' clause at all. The description reads as a persona statement rather than a skill description, failing to answer either question concretely.	1 / 5
Trigger Term Quality	Includes some relevant keywords like 'distributed systems', 'production incidents', and 'observability', but misses natural user phrases like 'error logs', 'stack trace', 'monitoring', 'alerting', 'tracing', 'metrics', or 'crash'.	3 / 5
Distinctiveness Conflict Risk	Very broad scope covering debugging, incident analysis, and observability — three potentially separate skill areas. High overlap risk with any debugging, monitoring, or incident response skills.	2 / 5
	Total	8 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/error-diagnostics-error-analysis/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.