tech-react
React-specific component, hook, and rendering patterns. Use when writing React components, hooks, JSX, or optimizing React performance.
74
Quality
62%
Does it follow best practices?
Impact
97%
1.18xAverage score across 3 eval scenarios
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 that clearly identifies its React-specific domain and provides explicit 'Use when' guidance with natural trigger terms. The main weakness is that the capabilities could be more concrete—listing specific actions like 'create custom hooks, implement context providers, optimize re-renders' rather than the more abstract 'patterns'.
Suggestions
Replace 'component, hook, and rendering patterns' with specific concrete actions like 'create custom hooks, implement context providers, optimize re-renders with memoization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React) and mentions some actions ('component, hook, and rendering patterns', 'writing React components, hooks, JSX', 'optimizing React performance'), but doesn't list multiple concrete specific actions like 'create custom hooks, implement memoization, manage component state'. | 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 seeking React help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on React with distinct triggers (React, JSX, hooks). Unlikely to conflict with general JavaScript or other framework skills due to explicit React focus. | 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 thin wrapper that delegates all actual React guidance to an external rules index while padding the file with generic troubleshooting content applicable to any skill. It fails to provide any concrete React patterns, code examples, or actionable guidance, making it nearly useless as a standalone reference for React development.
Suggestions
Add concrete React code examples for common patterns (hooks, memoization, component structure) directly in the skill file
Replace generic troubleshooting section with React-specific debugging guidance (e.g., identifying unnecessary re-renders, hook dependency issues)
Include at least a quick-start section with executable React code snippets before pointing to the rules index
Make the workflow React-specific with concrete validation steps like 'check for missing dependencies in useEffect' or 'verify memoization boundaries'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes boilerplate troubleshooting sections that are generic and not React-specific. The troubleshooting advice could apply to any skill and doesn't add React-specific value. | 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 usage 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 examples of what 'applying skill rules' means in practice. | 2 / 3 |
Progressive Disclosure | References an external rules index which is appropriate, but the main skill file contains almost no substantive content itself—it's essentially a pointer with generic troubleshooting filler rather than a useful overview. | 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 | |
- 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.