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.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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-hook-creator/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 extremely weak, consisting essentially of a title and auto-generated metadata with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms users would use, and lacks any 'Use when...' guidance. The repeated trigger term 'react hook creator' suggests auto-generation without human refinement.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates custom React hooks for state management, side effects, data fetching, and form handling. Extracts reusable logic from components into composable hooks.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a custom hook, refactor component logic into hooks, or mentions useState, useEffect, useCallback, useMemo, or React hooks.'
Include natural keyword variations users would actually say, such as 'custom hook', 'React hooks', 'useEffect', 'useState', 'hook pattern', 'composable logic', 'reusable hook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'React Hook Creator' but does not describe any concrete actions. There are no specific capabilities listed such as 'creates custom hooks', 'manages state logic', or 'extracts reusable logic from components'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'react hook creator' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'custom hook', 'useState', 'useEffect', 'React hooks', 'reusable hook', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The name 'React Hook Creator' narrows the domain somewhat to React hooks specifically, which provides some distinction from general frontend or React skills. However, the lack of specific actions means it could still overlap with broader React development 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 about creating React hooks. It contains only meta-descriptions of what the skill supposedly does without any concrete guidance, code examples, patterns, or workflows. Every section describes the skill abstractly rather than teaching Claude how to perform the task.
Suggestions
Replace the entire body with actual React hook creation guidance: include executable code examples of custom hooks (e.g., useDebounce, useFetch, useLocalStorage) with TypeScript types and usage patterns.
Add a concrete workflow for hook creation: 1) identify the stateful logic to extract, 2) define the hook signature and return type, 3) implement with proper dependency management, 4) write tests.
Include specific best practices as actionable rules (e.g., 'Always prefix with use', 'Return a tuple or object', 'Memoize callbacks with useCallback when passing to children') rather than vague claims about following best practices.
Remove all meta-content about when the skill activates and example triggers—this is frontmatter/system concern, not useful body content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'react hook creator' excessively, and contains zero substantive information about actually creating React hooks. | 1 / 3 |
Actionability | There is no concrete code, no executable examples, no specific commands, and no actual guidance on how to create React hooks. The content is entirely abstract meta-description with no actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints—just vague claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no structured navigation, and no bundle files. The content is a monolithic block of placeholder text with no meaningful organization of actual technical content. | 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.