react-component-generator
React Component Generator - Auto-activating skill for Frontend Development. Triggers on: react component generator, react component generator Part of the Frontend Development skill category.
36
3%
Does it follow best practices?
Impact
100%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/react-component-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a template placeholder with no substantive content. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The duplicated trigger term and boilerplate category mention provide almost no useful information for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates React functional components with TypeScript interfaces, props validation, hooks integration, and styled-components or CSS modules.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a React component, build a UI element in React, generate JSX, or scaffold a new component file.'
Remove the duplicated trigger term and expand with natural language variations users would actually say, such as 'React component', 'create component', 'JSX', 'React UI', 'functional component', '.tsx file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('React Component Generator', 'Frontend Development') but does not describe any concrete actions. There are no specific capabilities listed like 'creates functional components', 'generates props interfaces', or 'builds styled components'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is limited to a duplicated trigger phrase with no explicit 'Use when...' clause or meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'react component generator' repeated twice. This is a narrow, specific phrase unlikely to match natural user language like 'create a React component', 'build a component', 'JSX', 'React UI', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'React' and 'component generator' provides some specificity that distinguishes it from generic coding skills, but the lack of detail about what kind of components or what specific actions it performs could cause overlap with other React or frontend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content. It repeatedly references 'react component generator' without providing any concrete guidance, code examples, component patterns, or workflows. The entire file could be replaced by a single sentence and would convey the same (zero) amount of useful information.
Suggestions
Add concrete, executable React component code examples (e.g., functional component with TypeScript, hooks usage, prop typing) that Claude can use as templates.
Define a clear workflow for component generation: e.g., 1) Determine component type, 2) Set up file structure, 3) Implement component with specific patterns, 4) Add tests, 5) Validate accessibility.
Remove all meta-description boilerplate ('This skill provides automated assistance...', 'When to Use', 'Example Triggers') and replace with actual actionable content about React component patterns, best practices, and anti-patterns.
Include specific examples showing input (user request) → output (generated component code) to make the skill truly actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'react component generator' excessively, and provides zero substantive information about how to actually generate React components. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples, and no actual guidance on generating React components. The content is entirely abstract meta-description with no actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no sequences, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to support it either. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.