fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

3.22x

Quality

61%

Does it follow best practices?

Impact

100%

3.22x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/fix/SKILL.md

Quality

Content

80%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 concise and well-structured with concrete commands, but the pre-commit workflow lacks an explicit validation feedback loop, capping workflow clarity, and a likely command typo slightly reduces actionability.

Suggestions

Add a validation feedback loop: after `yarn linc`, instruct to fix errors and re-run until clean before committing.

Correct the likely typo `yarn linc` to `yarn lint` (or document it if intentional).

Make the final step more concrete by specifying how to report remaining manual fixes (e.g., list file:line with the lint rule).

Dimension	Reasoning	Score
Conciseness	The body is extremely lean: just numbered commands and brief mistake notes with no concept explanations or padding, so every token earns its place.	5 / 5
Actionability	Concrete copy-paste commands (`yarn prettier`, `yarn linc`) are provided, but the apparent typo 'linc' and the vague 'Report any remaining manual fixes needed' step leave minor gaps.	4 / 5
Workflow Clarity	Steps are numbered and sequenced, but a pre-commit CI-affecting workflow has no validate-fix-retry checkpoint, so the missing feedback loop caps this score at 3 per the rubric.	3 / 5
Progressive Disclosure	Under 50 lines with no external references needed, the body is well organized into Instructions and Common Mistakes sections, qualifying for the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

42%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 a clear, natural trigger clause but omits any statement of what the skill does, and its second-person voice triggers a specificity penalty. Trigger terms and distinctiveness are solid.

Suggestions

Add an explicit action statement of what the skill does, e.g. 'Fixes lint errors and reformats code...' before the 'Use when' clause.

Rewrite in third person ('Fixes lint errors and formatting issues. Use when...') to avoid the second-person voice penalty.

Add natural synonyms and tool names (linting, code style, prettier, eslint) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('lint errors, formatting issues', 'before committing code', 'passes CI') but states no concrete action verb describing what the skill does, and the second-person phrasing 'Use when you have...' triggers the voice penalty reducing the score by 1.	1 / 5
Completeness	A strong explicit 'when' clause is present ('Use when you have lint errors...'), but the 'what' — what the skill actually does — is entirely unstated, matching the anchor 'only when is present without what'.	2 / 5
Trigger Term Quality	Natural user phrases like 'lint errors', 'formatting issues', 'committing code', and 'passes CI' are present, but synonyms (linting, code style, prettier, eslint) and tool-specific terms are missing, so it stops short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The lint/format/pre-commit/CI niche is specific with distinct triggers, with only minor overlap risk against general git-commit or formatting skills.	4 / 5
	Total	11 / 20 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: facebook/react
Path: .claude/skills/fix/SKILL.md
Commit: eb8feb7

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.