CtrlK
BlogDocsLog inGet started
Tessl Logo

react-modernization

Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill is highly actionable with concrete executable code, but it is verbose and lacks an explicit in-body migration workflow with validation checkpoints for risky batch operations. Progressive disclosure is signaled but the main body is heavier than ideal.

Suggestions

Add an explicit numbered upgrade/migration workflow with validation checkpoints (e.g., run codemod dry-run, run test suite, verify build) to the body for risky batch operations.

Trim redundant full before/after component examples and move time-sensitive version breaking-change lists to references/details.md to improve conciseness.

Move performance optimization and TypeScript migration sections fully into the reference, keeping the body a lean overview with clear pointers.

DimensionReasoningScore

Conciseness

The body is largely executable code that assumes Claude's React knowledge, but it runs long (~320 lines) with multiple full before/after components and time-sensitive version breaking-change lists that could be tightened or moved to the reference.

2 / 3

Actionability

Provides fully executable, copy-paste-ready before/after code examples for hooks migration, the new root API, automatic batching, transitions, and Suspense.

3 / 3

Workflow Clarity

Content is organized by topic but the body lacks an explicit sequenced migration workflow with validation checkpoints; the migration checklist with feedback steps lives in the reference, and batch codemod operations have no inline validate/verify guidance.

2 / 3

Progressive Disclosure

A clearly signaled one-level-deep reference to references/details.md exists, but the body is heavy with extensive inline examples that overlap content also present in the reference, so the split could be cleaner.

2 / 3

Total

9

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capabilities and explicit use-when triggers with a well-defined niche. Trigger term coverage could be broader with common phrasings like 'React 18' or 'functional components'.

Suggestions

Add common trigger phrasings such as 'React 18', 'update React', and 'functional components' to broaden trigger_term_quality.

Consider mentioning codemods/automated refactoring in the description since it is a core capability covered in the skill body.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features' — matching the anchor listing several specific actions.

3 / 3

Completeness

Explicitly answers both what ('Upgrade... migrate... adopt') and when ('Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions').

3 / 3

Trigger Term Quality

Includes natural triggers like 'modernizing React codebases, migrating to React Hooks, upgrading to latest React versions', but omits common variations users would say such as 'React 18', 'functional components', or 'update React', so it is not comprehensive.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (React version upgrades and class-to-hooks migration) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.