typescript
TypeScript standards and best practices with modern tooling. Use when working with TypeScript or TypeScript React files.
59
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/typescript/SKILL.mdQuality
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 correctly uses third person voice and includes a 'Use when...' clause, which are positives. 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 'Enforces strict typing, creates interfaces and type definitions, configures tsconfig.json, uses generics appropriately'
Expand trigger terms to include file extensions and common TypeScript concepts: '.ts', '.tsx', 'type annotations', 'interfaces', 'generics', 'type errors'
Clarify what 'modern tooling' means by naming specific tools or patterns (e.g., 'ESLint with TypeScript parser', 'strict mode 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 standards but leans toward describing best practices rather than providing actionable, executable guidance. The organization and structure are good, but the content would benefit from concrete code examples demonstrating the patterns mentioned and trimming of concepts Claude already understands.
Suggestions
Add executable TypeScript code examples for key patterns (discriminated unions, Zod validation, dependency injection) instead of just describing them
Remove or condense well-known principles (DRY, KISS, SOLID, AAA pattern) that Claude already understands
Add a concrete workflow with validation steps: e.g., '1. Run pnpm tsc --noEmit 2. If errors, fix and re-run 3. Run pnpm test 4. Run pnpm lint'
| 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 general testing advice could be trimmed. | 2 / 3 |
Actionability | Provides specific tool recommendations and commands (pnpm format, pnpm lint), but lacks executable code examples. Most guidance is descriptive rather than showing concrete TypeScript patterns or copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | The Implementation section provides a basic sequence but lacks validation checkpoints. No explicit workflow for type checking, testing, or committing with feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and headers. References external file (pnpm-monorepo.md) appropriately. Content is structured for easy navigation without deep nesting. | 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.
- Repository
- siviter-xyz/dot-agent
- Commit
3376255
- 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.