CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

53

Quality

60%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

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 command and a basic workflow loop. Its main weakness is the workflow section, which could benefit from more explicit guidance on interpreting results (e.g., score thresholds) and a clearer validation checkpoint structure. Overall it's a solid simple skill that respects token budget.

Suggestions

Add guidance on interpreting the 0-100 score (e.g., what score ranges indicate pass/fail or acceptable quality) to strengthen the feedback loop.

Consider adding a brief note on what to do when specific categories (security vs performance vs correctness) fail, to make the fix-and-rerun loop more actionable.

DimensionReasoningScore

Conciseness

Very lean — no unnecessary explanations. Every line serves a purpose. Assumes Claude knows what React is and how npx works.

3 / 3

Actionability

Provides a concrete, copy-paste ready command with specific flags (--verbose --diff). The tool name and version strategy (@latest) are explicit.

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, guidance on interpreting the 0-100 score, or what constitutes passing vs failing thresholds.

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 bundle files are needed.

3 / 3

Total

11

/

12

Passed

Description

32%

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 fails to specify what concrete actions the skill performs — 'catch issues early' is too vague to be useful for skill selection. While it provides some trigger context with 'Use when...', the lack of specific capabilities makes it nearly impossible to distinguish from other React development skills like linting, testing, or code review tools.

Suggestions

Replace 'catch issues early' with specific actions the skill performs, e.g., 'Runs ESLint checks, executes unit tests, and validates TypeScript types for React components'.

Add distinctive trigger terms that differentiate this from other React skills, e.g., mention specific tools or checks like 'lint', 'test suite', 'build validation', or file types like '.tsx', '.jsx'.

Clarify the skill's niche to reduce conflict risk — is this a test runner, a linter, a build checker, or a combination? Being explicit will prevent it from being confused with other React-related skills.

DimensionReasoningScore

Specificity

The description says 'catch issues early' and 'Run after making React changes' but does not list any concrete actions like 'run linting', 'execute tests', 'check for type errors', etc. The actions are vague — what does 'catch issues' actually entail?

1 / 3

Completeness

It has a 'when' clause ('Use when reviewing code, finishing a feature, or fixing bugs in a React project'), but the 'what' is extremely weak — 'catch issues early' doesn't explain what the skill actually does. The when is present but the what is essentially missing.

2 / 3

Trigger Term Quality

Includes 'React', 'code', 'feature', 'bugs' which are somewhat relevant keywords users might say. However, it lacks specific terms like 'lint', 'test', 'build', 'type check', or other concrete trigger terms that would help distinguish what this skill actually does.

2 / 3

Distinctiveness Conflict Risk

This description is very generic and could conflict with many skills — linting, testing, type checking, code review, static analysis, etc. 'Reviewing code' and 'fixing bugs' are broad triggers that could match numerous other skills in a React development context.

1 / 3

Total

6

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.