lang-typescript
TypeScript language patterns and type safety rules — strict mode, no any, discriminated unions. Use when writing TypeScript code, reviewing types, or enforcing type safety.
70
Quality
58%
Does it follow best practices?
Impact
87%
0.96xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/universal/lang-typescript/SKILL.mdQuality
Discovery
82%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 has strong completeness with an explicit 'Use when...' clause and good trigger terms that users would naturally use. However, it lacks concrete action verbs describing what the skill does (e.g., 'validates', 'enforces', 'refactors') and instead lists constraints/rules. The distinctiveness could be improved by narrowing the scope beyond general 'writing TypeScript code'.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Enforces strict TypeScript patterns, validates type definitions, refactors code to eliminate any types'
Narrow the 'Use when' clause to reduce overlap with general coding skills, e.g., 'Use when enforcing strict typing rules, eliminating any types, or implementing discriminated unions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript) and mentions some patterns ('strict mode, no any, discriminated unions'), but these are more rules/constraints than concrete actions. Lacks action verbs describing what the skill actually does. | 2 / 3 |
Completeness | Clearly answers both what ('TypeScript language patterns and type safety rules') and when ('Use when writing TypeScript code, reviewing types, or enforcing type safety') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'TypeScript', 'types', 'type safety', 'strict mode'. Users would naturally say 'TypeScript code', 'reviewing types', or 'type safety' when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | While TypeScript-specific, it could overlap with general coding skills or other TypeScript-related skills. The focus on 'type safety rules' helps distinguish it, but 'writing TypeScript code' is broad enough to potentially conflict. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
35%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 reasonable high-level framework for TypeScript type safety but lacks the concrete, executable guidance that would make it actionable. The principles are sound but abstract, and much of the content is generic boilerplate (troubleshooting, workflow) that doesn't add TypeScript-specific value. The skill would benefit greatly from inline code examples demonstrating the patterns it advocates.
Suggestions
Add concrete code examples showing discriminated unions vs type assertions, and unknown narrowing with type guards
Remove or significantly condense the generic Troubleshooting and Workflow sections that apply to any skill
Include a brief inline example of strict mode configuration (tsconfig.json snippet)
Show before/after code for 'Replace unsafe any usage' to make the positive trigger example actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core principles are lean and efficient, but the boilerplate sections (Troubleshooting, Examples, Workflow) add significant padding with generic content that doesn't provide TypeScript-specific value. | 2 / 3 |
Actionability | No executable code examples, no concrete TypeScript patterns shown. The principles are abstract ('prefer discriminated unions') without demonstrating how. References external rules file without inline guidance. | 1 / 3 |
Workflow Clarity | The workflow section provides a 3-step sequence but it's generic meta-workflow about skill application, not a TypeScript-specific workflow. No validation checkpoints for type safety operations. | 2 / 3 |
Progressive Disclosure | References external rules index appropriately, but the main content is padded with generic troubleshooting that could be omitted. The structure exists but content balance is off. | 2 / 3 |
Total | 7 / 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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- 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.