react-hook-creator
React Hook Creator - Auto-activating skill for Frontend Development. Triggers on: react hook creator, react hook creator Part of the Frontend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill react-hook-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with minimal useful content. It relies entirely on the skill name without explaining capabilities, use cases, or providing natural trigger terms. The repeated trigger term and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates custom React hooks for state management, side effects, data fetching, and form handling'
Add a 'Use when...' clause with natural trigger terms like 'custom hook', 'useState', 'useEffect', 'React state', 'reusable logic', 'hook pattern'
Include concrete examples of hook types: 'useLocalStorage', 'useFetch', 'useDebounce', 'useForm' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('React Hook Creator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating custom hooks, managing state, handling side effects, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'react hook creator' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'custom hook', 'useState', 'useEffect', 'React hooks', or 'create a hook'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'React Hook' is somewhat specific to React development, the lack of detail means it could overlap with general React skills or frontend development skills. The category mention 'Frontend Development' is too broad to provide distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially an empty template with no actual instructional content. It describes what a React hook creator skill would do without providing any concrete guidance, code examples, or patterns for creating React hooks. The entire content is meta-description rather than actionable instruction.
Suggestions
Add concrete, executable code examples showing how to create common React hooks (useState wrappers, useEffect patterns, custom data fetching hooks)
Include specific patterns and anti-patterns for React hook creation with before/after examples
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual hook creation guidance
Add a quick reference section with hook rules (only call at top level, only call from React functions) and common hook signatures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'automated assistance for react hook creator tasks' and 'Follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually create React hooks. No code examples, no patterns, no specific instructions—just vague descriptions of what the skill supposedly does. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for creating React hooks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of unhelpful meta-description with no references to detailed materials, examples, or supporting documentation. There's nothing to disclose progressively because there's no substantive content. | 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.