typescript-language

Apply modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/typescript/typescript-language/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a terse, actionable TypeScript reference with executable examples and a verification checkpoint. Its main defect is the references bundle: REFERENCE.md points to three files that are absent from the repository.

Suggestions

Create references/advanced-types.md, references/type-guards.md, and references/utility-types.md, or remove their links from REFERENCE.md, so all referenced paths resolve.

Remove the empty '## Priority: P0 (CRITICAL)' header (it has no content beneath it) and consolidate the duplicate enum guidance between Implementation Guidelines and Anti-Patterns.

Add an explicit fix-and-reverify feedback loop to the Verification section (e.g., 'If getDiagnostics reports errors, fix them and re-run until clean') to reach a full validation cycle.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean terse bullets that assume Claude's TypeScript competence without explaining basics, with only minor redundancy (enum guidance repeated in Guidelines and Anti-Patterns, and an empty '## Priority: P0 (CRITICAL)' header) that could be trimmed.	4 / 5
Actionability	It provides executable code examples (branded types, satisfies, discriminated unions), specific anti-pattern fixes ('Use unknown instead of any'), and a concrete getDiagnostics verification step, but a few bullets are label-only ('Generics: Reusable, type-safe code') leaving minor gaps.	4 / 5
Workflow Clarity	The Verification section gives a clear checkpoint ('After any type change that crosses module boundaries... call getDiagnostics to confirm no type errors before finalizing'), but there is no explicit error-recovery feedback loop (fix and re-verify), so it sits below the level-5 anchor.	4 / 5
Progressive Disclosure	The body is well-sectioned with clearly signaled one-level references to references/REFERENCE.md and references/TESTING.md, but REFERENCE.md itself links to advanced-types.md, type-guards.md, and utility-types.md which do not exist in the bundle, leaving broken/dangling nested references that hurt navigation.	3 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and answers both what and when with concrete TypeScript trigger terms. Its main weakness is an abstract 'what' clause ('apply standards') rather than enumerated concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the TypeScript domain and the action 'Apply modern TypeScript standards' but that action is generic; it lists construct categories rather than multiple concrete capabilities, matching the 'names domain and 1-2 concrete actions' anchor rather than the multi-action level 4.	3 / 5
Completeness	It has both a 'what' ('Apply modern TypeScript standards for type safety and maintainability') and an explicit 'when' ('Use when working with types, interfaces, generics, enums, unions, or tsconfig settings') with concrete trigger phrases, but the 'what' is more abstract than the multi-action level-5 example.	4 / 5
Trigger Term Quality	'types, interfaces, generics, enums, unions, or tsconfig settings' gives good natural keyword coverage a developer would say, though it misses a few common synonyms/variations, fitting the 'good keyword coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The TypeScript-language niche with a tsconfig trigger is mostly distinct from other skills, with only minor overlap risk against general coding skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: .github/skills/typescript/typescript-language/SKILL.md
Commit: 405cdd5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.