tech-react
React-specific component, hook, and rendering patterns. Use when writing React components, hooks, JSX, or optimizing React performance.
74
62%
Does it follow best practices?
Impact
97%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/tech-react/SKILL.mdQuality
Discovery
89%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 solid skill description with explicit 'Use when' guidance and good trigger term coverage for React developers. The main weakness is that the capabilities section is somewhat abstract ('patterns') rather than listing concrete actions like creating components, managing state, or implementing specific hooks.
Suggestions
Replace 'patterns' with specific concrete actions like 'Create functional components, implement custom hooks, manage state with useState/useReducer, optimize re-renders with useMemo/useCallback'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React) and mentions some actions ('component, hook, and rendering patterns'), but doesn't list concrete specific actions like 'create functional components', 'implement custom hooks', or 'optimize re-renders with useMemo'. | 2 / 3 |
Completeness | Clearly answers both what ('React-specific component, hook, and rendering patterns') and when ('Use when writing React components, hooks, JSX, or optimizing React performance') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'React components', 'hooks', 'JSX', 'React performance'. These are terms developers naturally use when asking for React help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on React. The explicit mention of React, JSX, hooks, and React performance distinguishes it from general JavaScript or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a meta-template rather than actionable React guidance. It describes when to use the skill and generic troubleshooting but provides zero concrete React patterns, code examples, or specific technical guidance. The actual React knowledge appears to be entirely delegated to an external rules index, making this SKILL.md nearly useless on its own.
Suggestions
Add concrete React code examples for common patterns (hooks, memoization, component structure) directly in the skill body
Replace generic troubleshooting section with React-specific gotchas (stale closures, dependency arrays, key prop issues)
Include at least one executable code snippet showing a before/after refactoring pattern for re-render optimization
Expand the workflow with React-specific validation steps (e.g., 'verify useCallback dependencies', 'check for unnecessary re-renders')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes boilerplate troubleshooting sections that are generic and don't add React-specific value. The examples section explains obvious trigger/non-trigger scenarios that Claude would understand without explicit instruction. | 2 / 3 |
Actionability | The skill provides no concrete React code, patterns, or executable guidance. It only references an external rules index and describes meta-level workflow for skill selection rather than actual React implementation guidance. | 1 / 3 |
Workflow Clarity | The 3-step workflow is present but extremely generic ('identify', 'apply', 'validate'). It lacks React-specific steps, validation checkpoints, or concrete actions for component refactoring, hook optimization, or rendering improvements. | 2 / 3 |
Progressive Disclosure | References an external rules index which is appropriate, but the SKILL.md itself contains almost no substantive content - it's essentially a shell pointing elsewhere with generic troubleshooting filler. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- ravnhq/ai-toolkit
- Commit
7b466be
- 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.