typescript-best-practices
Provides TypeScript patterns for type-first development, making illegal states unrepresentable, exhaustive handling, and runtime validation. Must use when reading or writing TypeScript/JavaScript files.
84
Quality
77%
Does it follow best practices?
Impact
96%
1.11xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/typescript-best-practices/SKILL.mdQuality
Discovery
67%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 has a clear structure with both capability and trigger information, which is good. However, the capabilities are described at a conceptual level rather than concrete actions, and the trigger condition is overly broad ('Must use when reading or writing TypeScript/JavaScript files'), which would cause this skill to activate for nearly all TypeScript work regardless of whether type patterns are relevant.
Suggestions
Narrow the trigger condition to specific scenarios like 'Use when designing data models, handling union types, or adding runtime validation to TypeScript code'
Add more natural trigger terms users might say: 'type safety', 'type guards', 'discriminated unions', 'zod', 'type errors', '.ts files'
Make capabilities more concrete: instead of 'making illegal states unrepresentable', say 'design discriminated unions, create type guards, implement branded types'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript) and mentions patterns like 'type-first development', 'making illegal states unrepresentable', 'exhaustive handling', and 'runtime validation', but these are conceptual approaches rather than concrete actions like 'create interfaces' or 'add type guards'. | 2 / 3 |
Completeness | Clearly answers both what ('Provides TypeScript patterns for type-first development...') and when ('Must use when reading or writing TypeScript/JavaScript files') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'TypeScript' and 'JavaScript' which are natural terms users would say, but misses common variations like 'TS', 'JS', '.ts files', '.tsx', 'typing', 'types', or 'type errors' that users might naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | The trigger 'reading or writing TypeScript/JavaScript files' is extremely broad and would fire on virtually any TypeScript/JavaScript work, potentially conflicting with other skills that handle specific TS/JS tasks like testing, linting, or framework-specific patterns. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong TypeScript skill with excellent actionability and conciseness. The code examples are executable and demonstrate clear patterns. The main weakness is workflow clarity - while individual practices are well-documented, the skill could benefit from more explicit validation checkpoints when applying these patterns in sequence.
Suggestions
Add explicit validation/verification steps to the type-first development workflow (e.g., 'Run tsc --noEmit to verify types compile before implementing logic')
Include a brief checklist or feedback loop for catching common TypeScript errors during development
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's TypeScript competence. No unnecessary explanations of basic concepts; every section provides actionable patterns with minimal preamble. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Each pattern includes concrete TypeScript code with clear before/after comparisons and practical usage examples. | 3 / 3 |
Workflow Clarity | The type-first development section provides a clear 4-step workflow, but lacks explicit validation checkpoints or feedback loops. The instructions section lists practices without sequencing them into a coherent workflow for multi-step development tasks. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from fundamentals to advanced topics. Opens with a cross-reference to React skill, uses headers effectively, and the optional type-fest section is appropriately placed at the end with external link. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- 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.