CtrlK
BlogDocsLog inGet started
Tessl Logo

extract-errors

Use when adding new error messages to React, or seeing "unknown error code" warnings.

70

1.14x
Quality

60%

Does it follow best practices?

Impact

81%

1.14x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/extract-errors/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 body is admirably lean and appropriately sized for a simple skill, anchored by one concrete command. Its weakness is under-specification: the follow-up steps tell Claude what to determine but not how, leaving the actual code-assignment procedure undocumented.

Suggestions

Expand step 2 with the concrete procedure: what the `yarn extract-errors` output looks like and the exact edit that assigns a new code (file path and code format)

Clarify whether step 3 is a separate command or a check of the script output, and what 'up to date' means operationally

Add a brief validation checkpoint, e.g., re-run `yarn extract-errors` after assigning codes to confirm no uncoded errors remain

DimensionReasoningScore

Conciseness

The body is 13 lines with zero padding: a title, one section header, and three terse steps. Every token earns its place and nothing explains concepts Claude already knows.

5 / 5

Actionability

Step 1 is a concrete executable command ('Run `yarn extract-errors`'), but steps 2-3 ('Report if any new errors need codes assigned', 'Check if error codes are up to date') give no method — nothing about how to read the script output, where codes are stored, or how to assign a new code. Concrete guidance exists but key details are missing, matching anchor 3.

3 / 5

Workflow Clarity

A three-step sequence is present, but steps 2 and 3 are ambiguous (is 'Check if error codes are up to date' a separate action or interpreting the script output?) and there is no validation checkpoint. It sits above anchor 2 (a real sequence with a specific command exists) but below anchor 4 (steps are not clearly defined and lack checkpoints).

3 / 5

Progressive Disclosure

This is a simple skill under 50 lines with no need for external references, and it is cleanly sectioned ('# Extract Error Codes' / '## Instructions'). Per the rubric guideline for simple skills, well-organized sections alone merit a 5.

5 / 5

Total

16

/

20

Passed

Description

47%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 has strong, natural trigger phrasing and a distinctive niche, but it completely omits what the skill actually does. Adding a one-clause capability statement (e.g., 'Extracts and assigns error codes from React error messages') would move it from an only-'when' description to a complete one.

Suggestions

Add a 'what' clause before the 'Use when' clause, e.g., 'Runs the error-extraction script and assigns new error codes to uncoded React error messages. Use when...'

Include additional natural trigger variations such as 'assign error codes' or 'error codes are out of date' to broaden trigger coverage

Mention the codes file or invariant format so users searching for where codes are maintained also match this skill

DimensionReasoningScore

Specificity

The description names its domain ('adding new error messages to React', '"unknown error code" warnings') but states no actions the skill performs at all. It is not pure abstraction (anchor 1), but with zero concrete actions it cannot reach anchor 3.

2 / 5

Completeness

Only the 'when' is present ('Use when adding new error messages to React, or seeing "unknown error code" warnings') with no statement of what the skill does. This exactly matches anchor 2 ('only when is present without what').

2 / 5

Trigger Term Quality

Phrases like 'adding new error messages to React' and 'seeing "unknown error code" warnings' are natural things a user would say. Coverage is good but misses common variations such as 'assign error codes', 'invariant', or 'update error codes', keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The 'unknown error code' warning in a React context is a distinctive trigger unlikely to fire the wrong skill. Minor overlap risk with generic error-handling or linting skills keeps it below a clear-niche 5.

4 / 5

Total

12

/

20

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

Validation for skill structure

No warnings or errors.

Repository
facebook/react
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.