CtrlK
BlogDocsLog inGet started
Tessl Logo

react-development

Enforces React-specific patterns: functional components with hooks, TypeScript prop interfaces, CSS Modules co-location, React Testing Library behavioral tests. Use when creating React components, writing custom hooks, structuring component folders, applying RTL test patterns, or wiring TypeScript prop types. Trigger terms: React, .tsx, component, hook, RTL, jsx, useState, useEffect, prop interface

75

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, well-organized standards skill that assumes Claude's competence and provides concrete, executable verification commands. The only gap is a missing feedback-loop framing around the verification sequence and no full component code example.

Suggestions

Add an explicit feedback loop to the Verification block, e.g. "Fix all lint/typecheck errors before running tests; only build once tests pass."

Include one minimal runnable component example (props interface + functional component) to lift actionability from directives to copy-paste-ready code.

Clarify that the Verification commands are an ordered sequence (number them or add "then" connectors) so the workflow sequence is unambiguous.

DimensionReasoningScore

Conciseness

Lean bullet list, a four-command verification block, and a single security sentence — no padding and no explaining of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Concrete file-naming rules, an explicit export convention, copy-paste-ready commands (pnpm lint/typecheck/test/build), and a named tool (dompurify); falls just short of 5 because no full runnable component example is shown, only directives plus commands.

4 / 5

Workflow Clarity

A clear sequenced verification block (lint, typecheck, test, build) with a cross-reference to api-patterns for server validation; minor gap is the absence of an explicit "fix before proceeding" feedback loop on failure.

4 / 5

Progressive Disclosure

A single-purpose standards reference under 50 lines, organized into Conventions/Verification/Security with a clean one-level pointer to the api-patterns skill and no nested or buried references.

5 / 5

Total

18

/

20

Passed

Description

100%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.

A strong, specific description that clearly states what the skill enforces and when to use it, with comprehensive trigger terms and a distinct React-specific niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "functional components with hooks", "TypeScript prop interfaces", "CSS Modules co-location", "React Testing Library behavioral tests" — giving comprehensive coverage of the React domain.

5 / 5

Completeness

Explicitly answers both "what" ("Enforces React-specific patterns: ...") and "when" ("Use when creating React components, writing custom hooks, ...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms including file extensions and API names — React, .tsx, jsx, hook, RTL, useState, useEffect, prop interface — matching how users actually describe React work.

5 / 5

Distinctiveness Conflict Risk

A clearly bounded React-specific niche with distinct triggers (.tsx, useState, useEffect, RTL) and minimal overlap risk with non-React skills.

5 / 5

Total

20

/

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
monkilabs/opencastle
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.