typescript-language
Apply modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings. (triggers: **/*.ts, **/*.tsx, tsconfig.json, type, interface, generic, enum, union, intersection, readonly, const, namespace)
82
77%
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 ./.agent/skills/typescript/typescript-language/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 is a solid skill description with strong trigger term coverage and good completeness, clearly stating both what it does and when to use it. Its main weaknesses are that the capability description is somewhat abstract ('apply modern TypeScript standards') rather than listing concrete actions, and the broad file pattern triggers (*.ts, *.tsx) could cause it to activate for general TypeScript tasks that aren't specifically about type system features.
Suggestions
Replace the abstract 'Apply modern TypeScript standards' with specific concrete actions like 'Define strict type annotations, configure tsconfig compiler options, convert enums to const enums, apply utility types, and structure generic constraints'.
Consider narrowing the file pattern triggers or adding a note that this skill is specifically for type-system concerns rather than general TypeScript development, to reduce conflict risk with broader TypeScript skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (TypeScript standards) and mentions some areas (type safety, maintainability, types, interfaces, generics, enums, unions, tsconfig settings), but it doesn't list concrete actions like 'define strict type annotations', 'configure tsconfig compiler options', or 'refactor enums to const enums'. The actions are implied rather than explicitly stated. | 2 / 3 |
Completeness | Clearly answers both 'what' (apply modern TypeScript standards for type safety and maintainability) and 'when' (Use when working with types, interfaces, generics, enums, unions, or tsconfig settings), with explicit trigger terms listed. The 'Use when...' clause is present and specific. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file patterns (*.ts, *.tsx, tsconfig.json) and conceptual keywords (type, interface, generic, enum, union, intersection, readonly, const, namespace). These are terms users would naturally use when working with TypeScript type system features. | 3 / 3 |
Distinctiveness Conflict Risk | While the TypeScript type system focus is fairly specific, there could be overlap with general TypeScript coding skills or linting/formatting skills. The triggers like '*.ts' and '*.tsx' are very broad and would match any TypeScript work, not just type-system-specific tasks. However, the focus on types, interfaces, and generics helps narrow the niche somewhat. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise TypeScript patterns skill that efficiently communicates key conventions and anti-patterns. Its main weakness is that several bullet points are too terse to be fully actionable (e.g., 'Generics: Reusable, type-safe code' gives no concrete guidance), and the verification workflow lacks an explicit feedback loop for error recovery.
Suggestions
Expand the code examples section to include executable examples for type guards, discriminated union narrowing (switch statement), and a generic function—these are the patterns most likely to need concrete demonstration.
Add a feedback loop to the Verification section: e.g., 'If getDiagnostics reports errors: fix the type issue, re-run diagnostics, only finalize when clean.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every bullet point delivers actionable guidance without explaining what TypeScript is or how types work. No unnecessary preamble or padding—assumes Claude's competence throughout. | 3 / 3 |
Actionability | The code examples are concrete and executable, but most guidance is in terse bullet-point form (e.g., 'Generics: Reusable, type-safe code') that describes rather than instructs. More executable examples for key patterns like type guards, discriminated union switching, and generic usage would improve actionability. | 2 / 3 |
Workflow Clarity | The verification step mentioning getDiagnostics is a good checkpoint, but there's no clear sequenced workflow or feedback loop (e.g., what to do if diagnostics fail). For a skill that involves type changes crossing module boundaries, a validate-fix-retry loop would strengthen this. | 2 / 3 |
Progressive Disclosure | Clean overview structure with well-signaled one-level-deep references to TESTING.md and REFERENCE.md. Content is appropriately split between the main skill file and reference documents, with clear navigation links. | 3 / 3 |
Total | 10 / 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
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.