react-development
Enforces React-specific patterns: functional components with hooks, TypeScript prop interfaces, CSS Modules co-location, React Testing Library behavioral tests. Use when creating React components, writing custom hooks, structuring component folders, applying RTL test patterns, or wiring TypeScript prop types. Trigger terms: React, .tsx, component, hook, RTL, jsx, useState, useEffect, prop interface
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete capabilities, comprehensive trigger terms that developers would naturally use, explicit 'Use when' guidance, and a clearly defined niche around React development patterns. The description is concise yet thorough, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: functional components with hooks, TypeScript prop interfaces, CSS Modules co-location, React Testing Library behavioral tests. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (enforces React-specific patterns including functional components, hooks, TypeScript interfaces, CSS Modules, RTL tests) and 'when' (explicit 'Use when...' clause covering creating components, writing hooks, structuring folders, applying test patterns, wiring prop types). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: React, .tsx, component, hook, RTL, jsx, useState, useEffect, prop interface. These are terms developers naturally use when working with React and would trigger appropriate skill selection. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused on React-specific patterns. The combination of React, TypeScript, CSS Modules, and RTL creates a well-defined scope that is unlikely to conflict with general frontend, generic TypeScript, or non-React testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that efficiently communicates React development standards with executable examples, clear workflows, and explicit verification/error-recovery steps. It respects Claude's intelligence by avoiding explanations of basic concepts. The only minor weakness is the lack of progressive disclosure structure with supporting files, though the current content size doesn't strongly demand it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what React, TypeScript, or CSS Modules are, assumes Claude's competence, and every section delivers actionable guidance without padding. The comment about trimmed performance guidance shows intentional brevity. | 3 / 3 |
Actionability | Provides fully executable code examples for both component creation and testing, concrete bash commands for verification, and specific error recovery steps. The component example and test example are copy-paste ready. | 3 / 3 |
Workflow Clarity | The 'New Component Workflow' provides a clear 5-step sequence with a verification checkpoint at the end. The 'Verification commands + error recovery' section includes explicit feedback loops (if lint fails → fix → re-run; if typecheck fails → inspect → add types; if tests fail → runInBand → reproduce). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and appropriate inline brevity. However, there are no bundle files and only one cross-reference (to 'api-patterns' skill). Some sections like TypeScript and Styling could benefit from references to deeper guides if the content grows, but for the current size it's adequate. | 2 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.