react-modernization

Master React version upgrades, class to hooks migration, concurrent features adoption, and codemods for automated transformation.

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/react-modernization/SKILL.md

The canonical home for this skill is react-modernization in rmyndharis/antigravity-skills

Quality

Content

18%Scale 1-5

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

This skill is essentially a stub—it names a broad topic (React modernization) but provides no actionable content whatsoever. The instructions are entirely generic platitudes that could apply to any skill, and the sole referenced resource file does not exist in the bundle. A skill covering version upgrades, class-to-hooks migration, and concurrent features needs concrete code examples, migration workflows with validation steps, and specific codemod commands.

Suggestions

Add concrete, executable examples for the core use cases: at minimum a class-to-hooks migration example showing before/after code, and specific codemod commands (e.g., `npx react-codemod rename-unsafe-lifecycles`).

Define a clear multi-step workflow for React version upgrades with validation checkpoints (e.g., run tests after each step, check for deprecated API usage).

Replace the generic instructions ('Apply relevant best practices', 'Clarify goals') with React-specific guidance such as key breaking changes per version, dependency compatibility checks, and common pitfalls.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns directly in the SKILL.md.

Dimension	Reasoning	Score
Conciseness	The content is relatively short but includes generic filler instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') that add no value for Claude. The 'Use this skill when' and 'Do not use this skill when' sections are reasonable but the latter is particularly vacuous.	3 / 5
Actionability	The skill provides zero concrete guidance—no code examples, no specific commands, no migration patterns, no codemods. Every instruction is vague and abstract ('Apply relevant best practices', 'Provide actionable steps and verification'). It entirely delegates to a resource file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is no workflow, no sequenced steps, and no validation checkpoints. React version upgrades and class-to-hooks migrations are multi-step processes that need clear sequencing and verification, yet none is provided.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in principle. However, the bundle confirms no such file exists, making the reference broken. The SKILL.md itself contains almost no substantive content to serve as an overview, so the progressive disclosure structure fails in practice.	2 / 5
	Total	7 / 20 Passed

Description

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

The description does a good job listing specific React migration and upgrade capabilities, making it clear what the skill covers. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. The use of 'Master' as the opening verb is slightly informal but acceptable as third person imperative.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when upgrading React versions, migrating class components to functional components with hooks, adopting React 18 concurrent features, or running codemods.'

Include additional natural trigger terms and synonyms such as 'React 18', 'lifecycle methods', 'functional components', 'Suspense', 'useEffect', 'useState', or 'jscodeshift' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: 'React version upgrades', 'class to hooks migration', 'concurrent features adoption', and 'codemods for automated transformation'. These are concrete and domain-specific, though could be slightly more detailed about what each entails.	4 / 5
Completeness	Has a clear 'what' covering four specific capabilities, but completely lacks a 'when' clause or any explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes good natural keywords like 'React', 'hooks', 'class', 'migration', 'codemods', 'concurrent features', and 'version upgrades' that users would naturally use. Missing some variations like 'React 18', 'lifecycle methods', 'functional components', 'Suspense', or 'jscodeshift'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct with its focus on React migration and upgrades specifically. Could potentially overlap with a general React development skill, but the focus on version upgrades, class-to-hooks migration, and codemods narrows the scope well.	4 / 5
	Total	15 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/react-modernization/SKILL.md
Commit: 57c135b

Reviewed: 2 days 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.