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.
74
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/react-doctor/SKILL.mdQuality
Discovery
49%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 provides clear 'when' guidance with multiple trigger scenarios, which is a strength. However, it fails to specify what the skill actually does — 'catch issues early' is too vague to distinguish this from linting, testing, type-checking, or building skills. The lack of concrete actions makes it both non-specific and high-conflict-risk.
Suggestions
Replace 'catch issues early' with specific actions the skill performs, e.g., 'Runs ESLint, TypeScript checks, and unit tests on React components to catch issues early.'
Add more distinctive trigger terms related to the actual tooling, e.g., 'lint', 'test', 'type-check', 'build errors', '.tsx files'.
Narrow the scope to reduce conflict risk — specify whether this is about static analysis, testing, building, or a combination, so it won't overlap with other quality-assurance skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'catch issues early' and 'Run after making React changes' but never specifies what concrete actions the skill performs (e.g., run linting, run tests, type-check, build). The actions are vague — 'catch issues' is abstract. | 1 / 3 |
Completeness | It answers both 'what' (run after making React changes to catch issues early) and 'when' (when reviewing code, finishing a feature, or fixing bugs in a React project), with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes 'React', 'code', 'feature', 'bugs', and 'reviewing code' which are somewhat natural terms, but lacks specifics like 'lint', 'test', 'type check', 'build', 'CI', or file extensions that would help distinguish this skill's purpose. | 2 / 3 |
Distinctiveness Conflict Risk | Very generic — 'catch issues early' in a 'React project' could overlap with linting skills, testing skills, build skills, code review skills, or any quality-assurance-related skill. There's no clear niche. | 1 / 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 concise, actionable skill that provides a clear single command and a brief workflow. Its main weakness is that the workflow section could benefit from slightly more guidance on interpreting results and deciding when the score is acceptable, though for such a simple tool-invocation skill it performs well overall.
Suggestions
Add brief guidance on interpreting the output (e.g., 'Score above 80 is acceptable; focus on errors marked [critical] first') to strengthen the workflow's validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean — every token earns its place. No unnecessary explanation of what React is or how npx works. The description and command are minimal and sufficient. | 3 / 3 |
Actionability | Provides a fully copy-paste ready command with specific flags (--verbose --diff). Claude can execute this immediately without any ambiguity. | 3 / 3 |
Workflow Clarity | The workflow mentions running, fixing errors, and re-running to verify improvement, which is a basic feedback loop. However, it lacks explicit validation checkpoints — e.g., what constitutes a passing score, how to interpret the output, or what to do if specific error categories appear. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (Usage, Workflow). No unnecessary nesting or missing structure. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
05d40bb
- 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.