This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).
95
Does it follow best practices?
Evaluation — 95%
↑ 1.15xAgent success when using this skill
Validation for skill structure
Discovery
89%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 is a strong skill description that clearly identifies its niche (React + TypeScript) and provides explicit trigger guidance. The description includes good keyword coverage for discoverability and clearly distinguishes itself from generic React or TypeScript skills. The main weakness is that the specific capabilities could be more concrete (e.g., what specific patterns or solutions it provides).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React with TypeScript) and mentions some actions like 'building React components', 'typing hooks', 'handling events', but doesn't list comprehensive concrete actions. Terms like 'type-safe patterns' and 'routing integration' are somewhat vague. | 2 / 3 |
Completeness | Explicitly answers both what ('building React components with TypeScript, typing hooks, handling events, type-safe patterns, routing integration') and when ('should be used when building React components with TypeScript... or when React TypeScript, React 19, Server Components are mentioned'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'React components', 'TypeScript', 'hooks', 'events', 'React 19', 'Server Components', 'TanStack Router', 'React Router', 'generic components'. These are terms developers naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining React + TypeScript specifically, with distinct version markers (React 18-19) and specific router libraries. Unlikely to conflict with general React skills or general TypeScript skills due to the explicit combination and version specificity. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while providing comprehensive, actionable guidance for React TypeScript development. The content is well-organized with clear sections, executable code examples, and appropriate progressive disclosure through well-signaled references. The ALWAYS/NEVER rules section provides clear guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with TypeScript and React. Every section provides direct, actionable patterns without explaining basic concepts like what React or TypeScript are. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. The skill provides specific, concrete patterns for every use case including component props, event handlers, hooks, generics, and routing with real TypeScript syntax. | 3 / 3 |
Workflow Clarity | For a reference/pattern skill, the workflow is clear through well-organized sections. The ALWAYS/NEVER rules provide explicit guidance, and the when_to_use section clearly scopes applicability. No multi-step destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise inline examples and clear one-level-deep references to detailed materials (hooks.md, event-handlers.md, etc.). Each section provides enough to get started while pointing to comprehensive references for advanced needs. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.