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.

80

1.04x
Quality

70%

Does it follow best practices?

Impact

100%

1.04x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/framework-migration/skills/react-modernization/SKILL.md

The canonical home for this skill is react-modernization in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 rich with executable before/after code and real codemod commands, but it is over-long for a SKILL.md, includes general React performance padding, and critically advertises six bundle files that do not exist. Workflow sequencing is decent yet lacks the validate-and-retry loop that batch codemod operations demand.

Suggestions

Create the referenced bundle files (references/breaking-changes.md, references/codemods.md, references/hooks-migration.md, references/concurrent-features.md, assets/codemod-config.json, assets/migration-checklist.md, scripts/apply-codemods.sh) or remove the broken references from the Resources section.

Move the detailed version-specific breaking-change lists and full hooks-migration patterns into the referenced files, leaving SKILL.md as a concise overview that links out one level deep.

Add an explicit validation feedback loop for codemods (e.g., run codemod → run test suite → if failures, review diff and fix → re-run tests) and complete the custom codemod example's transformation logic.

Trim or move the general useMemo/useCallback, React.memo, and code-splitting sections, which restate React performance knowledge Claude already has rather than modernization-specific guidance.

DimensionReasoningScore

Conciseness

Mostly efficient code patterns, but sections on useMemo/useCallback, React.memo, and code splitting restate general React performance concepts Claude already knows, and the 527-line body could be trimmed.

3 / 5

Actionability

Mostly copy-paste ready before/after examples and runnable npx codemod commands, but the custom codemod example leaves transformation logic as '// ... transformation logic', a minor gap.

4 / 5

Workflow Clarity

A sequenced Migration Checklist exists and codemods include a --dry preview, but batch codemod transforms lack an explicit validate-tests-then-fix-retry feedback loop, which caps batch-operation workflow clarity at 3.

3 / 5

Progressive Disclosure

The Resources section lists references/breaking-changes.md, references/codemods.md, assets/codemod-config.json, scripts/apply-codemods.sh and more, but none of the references/, assets/, or scripts/ directories exist — the references are broken — while large blocks that belong in those files are inlined.

2 / 5

Total

12

/

20

Passed

Description

87%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.

A strong, third-person description that clearly states both capabilities and trigger conditions with concrete, natural language. It is held back only slightly from full marks by a few missing synonyms and the omission of codemods/TypeScript which the body covers.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features' — but omits codemods/TypeScript covered in the body, so minor gaps remain.

4 / 5

Completeness

Explicitly answers both what ('Upgrade React applications... migrate from class components to hooks, and adopt concurrent features') and when ('Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions') but misses common synonyms like 'class to hooks' or 'React 18'.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (React version upgrades and class-to-hooks migration) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (527 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.