typescript-pro

Master TypeScript with advanced types, generics, and strict type safety. Handles complex type systems, decorators, and enterprise-grade patterns.

Quality

31%

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 ./skills/typescript-pro/SKILL.md

Quality

Content

21%Scale 1-5

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

This skill reads as a high-level overview of TypeScript expertise areas rather than actionable guidance. It lacks any concrete code examples, specific compiler flags, tsconfig configurations, or executable patterns — everything Claude would actually need to perform differently. The content mostly restates what Claude already knows about TypeScript without adding project-specific or novel instructions.

Suggestions

Add concrete, executable code examples for key patterns (e.g., a generic utility type, a conditional type pattern, a decorator example) instead of just listing concept names.

Include a specific tsconfig.json snippet with recommended strict settings and explain any non-obvious choices.

Replace vague workflow steps like 'Model types and contracts for critical surfaces' with concrete actions, e.g., 'Define shared API types in a `types/` directory using interface-first design' with an example.

Remove the 'Focus Areas' bullet list entirely — Claude already knows these TypeScript concepts — and replace with specific patterns or anti-patterns unique to this skill's intended use.

Dimension	Reasoning	Score
Conciseness	The skill extensively lists concepts Claude already knows well (generics, conditional types, mapped types, utility types, etc.) without adding novel information. The 'Focus Areas' and 'Approach' sections are padded with general TypeScript knowledge that doesn't teach Claude anything new.	2 / 5
Actionability	The skill contains zero concrete code examples, no executable commands, no specific tsconfig settings, and no copy-paste ready patterns. Every instruction is abstract and vague — e.g., 'Model types and contracts for critical surfaces' gives no actionable guidance on how to do so.	1 / 5
Workflow Clarity	The four numbered steps in 'Instructions' provide a rough sequence but are extremely vague with no concrete actions, no validation checkpoints, and no feedback loops. 'Validate build performance and developer ergonomics' is not an actionable validation step.	2 / 5
Progressive Disclosure	The content is organized into sections (Instructions, Focus Areas, Approach, Output) which provides some structure, but there are no references to external files and the content that could benefit from deeper treatment (e.g., advanced type patterns, tsconfig examples) is neither inlined with substance nor referenced elsewhere.	3 / 5
	Total	8 / 20 Passed

Description

41%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 identifies the TypeScript domain and lists several relevant topic areas but relies on vague, buzzword-heavy language ('enterprise-grade patterns', 'master TypeScript') rather than concrete actions. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. The trigger terms are decent but incomplete, missing common user phrases and file extensions.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about TypeScript types, generics, interfaces, type errors, .ts files, or type-safe patterns.'

Replace vague language like 'Master TypeScript' and 'enterprise-grade patterns' with concrete actions such as 'Defines complex generic types, creates type guards, implements utility types, configures strict tsconfig settings.'

Include additional natural trigger terms users would say, such as 'type errors', 'interfaces', 'type narrowing', 'utility types', '.ts', and 'type inference'.

Dimension	Reasoning	Score
Specificity	Names the domain (TypeScript) and mentions several concepts (advanced types, generics, strict type safety, decorators, enterprise-grade patterns), but these are more like topic areas than concrete actions. There are no specific verbs describing what the skill does beyond the vague 'Handles.'	3 / 5
Completeness	Has a somewhat vague 'what' (master TypeScript, handles complex type systems) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which per the rubric caps completeness at 3, and the 'what' is also not very clear, placing it at 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'TypeScript', 'generics', 'decorators', and 'type safety' that users might mention, but misses common natural phrases like 'type errors', 'interfaces', 'type narrowing', 'utility types', '.ts files', or 'type inference' that users would naturally say.	3 / 5
Distinctiveness Conflict Risk	TypeScript is a specific enough domain, but 'enterprise-grade patterns' and 'advanced types' are broad enough to overlap with general coding skills or JavaScript skills. The description doesn't clearly carve out a niche distinct from a general TypeScript or JavaScript coding skill.	3 / 5
	Total	11 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/typescript-pro/SKILL.md
Commit: debb2ec

Reviewed: 10 hours 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.