extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
62
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 focuses almost entirely on trigger conditions while neglecting to explain what the skill actually does. While the 'Use when...' clause is present and contains some useful trigger terms around React error messages, the complete absence of capability description (what actions the skill performs) makes it difficult for Claude to understand the skill's purpose and for users to know what to expect.
Suggestions
Add specific actions the skill performs, e.g., 'Generates standardized error codes, updates the error message catalog, and creates user-facing error text for React applications.'
Expand trigger terms to include variations like 'error codes', 'error handling', 'React errors', 'error catalog', or specific file patterns if applicable.
Restructure to lead with capabilities before the 'Use when...' clause to clearly communicate what the skill does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions - it only mentions 'adding new error messages' without specifying what the skill actually does (e.g., generates error codes, updates error catalogs, creates error handling). | 1 / 3 |
Completeness | Has a 'Use when...' clause addressing when to use it, but the 'what does this do' component is essentially missing - we know when to trigger it but not what actions the skill performs. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'React', 'error messages', and 'unknown error code warnings' that users might naturally mention, but missing variations like 'error handling', 'error codes', or specific React error patterns. | 2 / 3 |
Distinctiveness Conflict Risk | The React + error messages combination provides some specificity, but 'error messages' is broad enough to potentially conflict with general error handling or logging skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is admirably concise and provides a clear starting command, but falls short on actionability and workflow clarity. Steps 2 and 3 are vague—Claude won't know what output to expect, how to determine if errors need codes, or what 'up to date' means in practice.
Suggestions
Add expected output examples from `yarn extract-errors` showing what 'new errors needing codes' looks like
Specify concrete actions for step 2: what file to check, what format codes should be in, how to assign them
Clarify step 3: what does 'up to date' mean and how to verify it (e.g., compare against a specific file or run a validation command)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean with no unnecessary explanation. Every line serves a purpose and assumes Claude knows what error codes and yarn commands are. | 3 / 3 |
Actionability | Provides a concrete command but lacks detail on what to do after running it—how to interpret output, what 'assigning codes' means, or how to check if codes are 'up to date'. | 2 / 3 |
Workflow Clarity | Steps are listed but vague. 'Report if any new errors need codes assigned' and 'Check if error codes are up to date' lack concrete actions, expected outputs, or validation criteria. | 1 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the flat structure is appropriate. No need for external references given the scope. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.