react-doctor

Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.

Quality

63%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/react-doctor/SKILL.md

Quality

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 fails to explain what the skill actually does - it only describes when to run it and a vague outcome ('catch issues early'). The lack of concrete actions (linting, testing, type checking, etc.) makes it impossible for Claude to understand the skill's actual capabilities and distinguish it from other React-related skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Runs ESLint, TypeScript checks, and Jest tests on React components'

Include natural trigger terms users would say like 'lint', 'test', 'check my code', 'run tests', 'validate'

Specify what types of issues it catches (type errors, lint violations, test failures) to improve distinctiveness

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'catch issues early' and 'making React changes' without specifying concrete actions. It doesn't describe what the skill actually does (e.g., runs linting, type checking, tests, etc.).	1 / 3
Completeness	Has a 'Use when...' clause covering when to use it, but the 'what' is extremely weak - 'catch issues early' doesn't explain what the skill actually does or what kind of issues it catches.	2 / 3
Trigger Term Quality	Includes 'React', 'reviewing code', 'feature', 'fixing bugs' which are somewhat relevant keywords, but misses specific terms users might say like 'lint', 'test', 'check', 'validate', or 'CI'.	2 / 3
Distinctiveness Conflict Risk	Mentions React specifically which helps narrow scope, but 'reviewing code' and 'fixing bugs' are generic enough to potentially conflict with other code review or testing skills.	2 / 3
	Total	7 / 12 Passed

Implementation

87%

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

This is a well-crafted, concise skill that provides immediately actionable guidance for running react-doctor. Its main strength is token efficiency and a ready-to-use command. The workflow section could benefit from slightly more detail on interpreting results or handling common error patterns.

Suggestions

Add brief guidance on interpreting the 0-100 score (e.g., what score ranges indicate healthy vs problematic codebases)

Consider adding 1-2 examples of common diagnostic outputs and how to address them

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Every line serves a purpose with no unnecessary explanation of what React is or how npx works. Assumes Claude's competence appropriately.	3 / 3
Actionability	Provides a complete, copy-paste ready command with specific flags (--verbose --diff). The command is fully executable and requires no interpretation.	3 / 3
Workflow Clarity	Basic workflow is present (run -> fix errors -> re-run to verify), but lacks explicit validation checkpoints or guidance on what to do if specific error types occur. For a tool that outputs diagnostics, more guidance on interpreting results would strengthen this.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines, this is appropriately structured. Clear sections with quick start usage and workflow guidance. No need for external references given the scope.	3 / 3
	Total	11 / 12 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: freekmurze/dotfiles
Commit: 355d067

Reviewed: 1 day 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.