react-development
Enforces naming conventions, prop typing patterns, file structure, and test coverage standards. Use when creating or modifying React components, custom hooks, or component tests. Trigger terms: React app, .tsx files, testing library, custom hooks, functional components
100
100%
Does it follow best practices?
Impact
Pending
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 a well-crafted skill description that clearly communicates specific capabilities (naming conventions, prop typing, file structure, test coverage), provides explicit 'Use when' guidance, and includes natural trigger terms. It follows third-person voice and is concise without being vague. It serves as a strong example of how to write a skill description that enables accurate skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: enforcing naming conventions, prop typing patterns, file structure, and test coverage standards. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (enforces naming conventions, prop typing, file structure, test coverage) and 'when' (creating/modifying React components, custom hooks, or component tests), with an explicit 'Use when' clause and trigger terms. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'React app', '.tsx files', 'testing library', 'custom hooks', 'functional components'. These cover common variations of how users would describe React development tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to React-specific conventions and patterns with distinct triggers like '.tsx files', 'testing library', and 'custom hooks'. Unlikely to conflict with general coding or non-React skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers React development standards with concrete, executable examples and clear workflows. It respects token budget by assuming Claude's knowledge of React fundamentals while providing specific project conventions. The error recovery section with feedback loops and the well-structured component workflow are particular strengths.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what React, TypeScript, or CSS Modules are, and assumes Claude's competence. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples for both component creation and testing, specific bash commands for verification, and concrete patterns like the UserCard interface/component. The guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | The 'New Component Workflow' provides a clear 5-step sequence with a verification step. The 'Verification commands + error recovery' section includes explicit feedback loops (lint fails → fix → re-run, typecheck fails → inspect → add types, tests fail → runInBand → reproduce). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, appropriately concise inline content, and one-level-deep references to REFERENCE.md for TypeScript patterns and api-patterns for validation. No monolithic walls or deeply nested references. | 3 / 3 |
Total | 12 / 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
18c6f2c
- 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.