typescript-pro
Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill typescript-proOverall
score
64%
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
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 trigger term coverage and completeness with explicit 'Use when' and 'Invoke for' clauses. However, it lacks concrete action verbs describing what the skill actually does (e.g., 'implements', 'configures', 'generates') and could potentially overlap with general TypeScript skills due to its broad scope.
Suggestions
Add concrete action verbs to describe capabilities (e.g., 'Implements type guards, creates utility types, configures tRPC endpoints, sets up monorepo type sharing')
Clarify the boundary with basic TypeScript skills by emphasizing what makes this 'advanced' (e.g., 'complex generic constraints', 'conditional types', 'mapped types')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript) and lists several specific concepts (type guards, utility types, tRPC integration, monorepo setup), but these are more like feature keywords than concrete actions. Missing action verbs like 'create', 'implement', or 'configure'. | 2 / 3 |
Completeness | Explicitly answers both what (building TypeScript applications with advanced type systems) and when ('Use when building TypeScript applications...', 'Invoke for type guards, utility types...'). Has clear trigger guidance with 'Use when' and 'Invoke for' clauses. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'TypeScript', 'generics', 'type guards', 'utility types', 'tRPC', 'monorepo', 'full-stack type safety'. These are terms developers naturally use when seeking TypeScript help. | 3 / 3 |
Distinctiveness Conflict Risk | While TypeScript-specific terms like 'tRPC' and 'type guards' are distinctive, 'building TypeScript applications' is broad and could overlap with general JavaScript/TypeScript skills. The 'advanced type systems' qualifier helps but doesn't fully prevent conflicts. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization with clear progressive disclosure through the reference table, but critically lacks actionable content. The absence of any executable TypeScript code examples severely limits its utility - it tells Claude what concepts exist but not how to implement them. The constraints section provides useful guardrails but would benefit from concrete examples showing correct vs incorrect patterns.
Suggestions
Add executable TypeScript code examples for key patterns (branded types, type guards, discriminated unions) - at minimum 2-3 copy-paste ready snippets
Replace the abstract 'Knowledge Reference' keyword list with a concrete example showing a complete type-safe pattern implementation
Add validation checkpoints to the workflow, such as specific tsc commands or type coverage thresholds to verify success
Remove the verbose role definition paragraph and 'years of experience' framing - Claude doesn't need persona backstory
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('Senior TypeScript specialist with 10+ years of experience') and verbose role definition that Claude doesn't need. The reference table and constraints are reasonably efficient, but the 'Knowledge Reference' section is just a keyword list that adds little value. | 2 / 3 |
Actionability | The skill lacks any concrete, executable code examples. It describes what to do ('Create branded types', 'Implement type guards') but provides no actual TypeScript code, patterns, or copy-paste ready examples. The guidance is entirely abstract and descriptive. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence but lacks validation checkpoints or feedback loops. Steps like 'Test types' and 'Verify type coverage' are mentioned but not explained with concrete validation commands or criteria for success. | 2 / 3 |
Progressive Disclosure | The reference table provides clear, one-level-deep navigation to specific topics with explicit 'Load When' guidance. The structure separates overview content from detailed references appropriately, making it easy to find relevant information. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 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.