CtrlK
BlogDocsLog inGet started
Tessl Logo

you-dont-need-react-custom-hooks

Use when React component or custom hook work may involve extracting hooks, changing hook responsibilities, or hiding dependencies behind custom hooks

63

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/you-dont-need-react-custom-hooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable judgment framework with concrete good/bad code examples and clear decision criteria; its only weaknesses are mild restatement across the rules/mistakes/final-rule sections and the absence of any progressive-disclosure reference files.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic React/hook explanations) and uses dense tables and code, with only minor trimmable repetition — the "Final Rule" and "Common Mistakes" table largely restate "Core Rules" and "Invalid Reasons".

4 / 5

Actionability

Provides copy-ready TypeScript examples covering the common cases (useDisclosure, useOnClickOutside, bad-vs-good useCartTotalPrice, thin wrappers, the useUserProfile smell with its inline alternative) plus concrete decision questions and lookup tables.

5 / 5

Workflow Clarity

A clear decision workflow is laid out — the four Core Rules questions, alternatives-to-consider-first table, invalid-reasons table, and always-good/always-bad/judgment categories — with an effective checklist, though it is a judgment framework rather than a checkpointed pipeline.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Overview, When to Use, Core Rules, Alternatives, Always Good/Bad, Judgment, Controller Pattern, Common Mistakes, Final Rule) with no buried references; content is cohesive in one file, though the >50-line body carries no one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description opens with a strong, concrete "Use when..." trigger naming the domain and specific situations, but it omits any explicit statement of what the skill does, leaving the "what" implied rather than stated.

Suggestions

Lead with a short "what" clause before the trigger, e.g. "Evaluates whether React logic should be a custom hook versus an ordinary function or component-local logic. Use when..." so the skill's purpose is explicit.

Add a couple of natural synonyms developers use, such as "refactoring hooks" or "useX hooks", to broaden trigger coverage.

Consider noting the negative trigger ("Do not use for ordinary non-React functions") in the description to further reduce overlap with general refactoring skills.

DimensionReasoningScore

Specificity

Names the React custom-hook domain plus three concrete situations — "extracting hooks, changing hook responsibilities, or hiding dependencies behind custom hooks" — giving several specific triggers, though they describe situations rather than a comprehensive set of capabilities.

4 / 5

Completeness

The "when" is explicit and concrete ("Use when React component or custom hook work may involve..."), but the description never states what the skill actually does — the "what" is only implied by the trigger conditions, mirroring the anchor-3 gap in reverse.

3 / 5

Trigger Term Quality

Uses natural developer terms ("React component", "custom hook", "extracting hooks", "hook responsibilities") that a user would plausibly say, with good coverage but a few common synonyms (e.g. "refactoring hooks", "useX") missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear React custom-hook niche with specific triggers, carrying only minor overlap risk with general React refactoring or component-design skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
choegyumin/agent-skills
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.