typescript
TypeScript standards and best practices with modern tooling. Use when working with TypeScript or TypeScript React files.
60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 identifies the technology domain (TypeScript) and includes a 'Use when' clause, which is positive. However, it fails to specify concrete actions Claude will perform and relies on vague terms like 'standards and best practices' and 'modern tooling' without explaining what these mean in practice.
Suggestions
Replace 'standards and best practices with modern tooling' with specific actions like 'Define interfaces, create type guards, configure tsconfig, apply strict typing patterns'
Add more trigger term variations such as '.ts', '.tsx', 'type annotations', 'interfaces', 'generics', 'type errors'
Expand the 'Use when' clause to include specific scenarios like 'when adding types to JavaScript code, fixing type errors, or setting up TypeScript configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'standards and best practices with modern tooling' without listing any concrete actions. It doesn't specify what actions Claude will perform (e.g., type checking, interface creation, generic usage). | 1 / 3 |
Completeness | Has a weak 'what' (standards and best practices) and includes a 'Use when...' clause, but the 'what' is too vague to be meaningful. The trigger guidance exists but the capability description is insufficient. | 2 / 3 |
Trigger Term Quality | Includes 'TypeScript' and 'TypeScript React files' which are relevant keywords users might mention, but misses common variations like '.ts', '.tsx', 'TS', 'type annotations', 'interfaces', or 'generics'. | 2 / 3 |
Distinctiveness Conflict Risk | TypeScript is a specific technology which helps distinctiveness, but 'standards and best practices' is generic enough to potentially overlap with general coding skills or JavaScript skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive overview of TypeScript best practices with good organization and clear section structure. However, it leans heavily on descriptive guidance rather than executable examples, and includes some concepts Claude already understands. The lack of concrete code snippets demonstrating the patterns reduces actionability.
Suggestions
Add executable TypeScript code examples for key patterns (discriminated unions, Zod validation, dependency injection) instead of just describing them
Remove explanations of well-known principles (DRY, KISS, SOLID, AAA pattern) that Claude already understands - just reference them by name
Add a concrete workflow with validation steps: e.g., '1. Run `pnpm tsc --noEmit` 2. If errors, fix type issues 3. Run `pnpm lint` 4. Run `pnpm test`'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some guidance Claude already knows (DRY, KISS, SOLID principles, basic testing patterns like AAA). Some sections like 'Design Principles' and 'Testing Quality' explain concepts that don't need explanation. | 2 / 3 |
Actionability | Provides specific tool recommendations and config values (Prettier settings, pnpm commands), but lacks executable code examples. Most guidance is descriptive ('use union types', 'prefer composition') rather than showing concrete TypeScript patterns with actual code. | 2 / 3 |
Workflow Clarity | The 'Implementation' section provides a basic workflow but lacks validation checkpoints. No explicit steps for type-checking verification or how to handle failures. The guidance is more a list of principles than a clear sequence with feedback loops. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and headers. References external file (pnpm-monorepo.md) appropriately at the end. Content is appropriately structured without deep nesting, and sections are logically grouped by concern. | 3 / 3 |
Total | 9 / 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.
- 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.