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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill react-component-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The redundant trigger terms and boilerplate structure ('Auto-activating skill for...', 'Part of the...') add no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates React functional components with TypeScript support, prop interfaces, and optional styling (CSS modules, styled-components)'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to create a React component, needs JSX boilerplate, wants to scaffold a new UI element, or mentions component generation'
Remove redundant trigger terms and add variations users would naturally say: 'create component', 'new React component', 'component template', 'JSX', 'functional component'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('React Component Generator', 'Frontend Development') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating components, generating boilerplate, handling props, styling, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause or equivalent guidance. The 'Triggers on' section is not a proper when clause - it just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('react component generator' listed twice) and overly specific. Missing natural variations users would say like 'create react component', 'new component', 'JSX', 'functional component', 'class component', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'React Component Generator' is somewhat specific to React, the lack of detail about what it generates or how it differs from general React development skills creates potential overlap with other frontend or React-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what a React component generator skill might do in abstract terms but provides zero concrete guidance, code examples, or actionable steps. The content fails on all dimensions by being verbose yet empty of substance.
Suggestions
Add executable code examples showing how to generate React components (e.g., functional component template, component with props/state, component with hooks)
Include specific patterns and conventions (naming conventions, file structure, prop-types or TypeScript interfaces)
Provide concrete workflow steps: 1) Determine component type, 2) Generate boilerplate, 3) Add props interface, 4) Implement logic, 5) Add tests
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to generate React components. The entire content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no processes, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed materials, no examples, and no clear organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.