typescript-advanced-types

Comprehensive guidance for mastering TypeScript's advanced type system including generics, conditional types, mapped types, template literal types, and utility types for building robust, type-safe applications.

Quality

38%

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-advanced-types/SKILL.md

The canonical home for this skill is typescript-advanced-types in rmyndharis/antigravity-skills

Quality

Content

25%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 is essentially a hollow placeholder. It contains no actionable TypeScript content whatsoever — no code examples, no type patterns, no concrete guidance on generics, conditional types, mapped types, or any of the topics it claims to cover. The instructions are generic boilerplate that could apply to any domain, and the sole referenced resource file does not exist in the bundle.

Suggestions

Add concrete, executable TypeScript code examples demonstrating at least the core patterns (generics, conditional types, mapped types, template literal types) directly in the SKILL.md.

Replace the generic instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') with specific, actionable guidance for working with TypeScript's type system.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential content so the skill is self-contained.

Remove the repeated description and trim the 'Use this skill when' list to only the most relevant scenarios to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The description is repeated from the frontmatter, and the 'Use this skill when' / 'Do not use this skill when' sections are padded with generic items. The instructions section is extremely generic and could apply to almost any skill. However, it's not excessively verbose overall.	3 / 5
Actionability	There is zero concrete guidance — no code examples, no specific type patterns, no executable snippets, no commands. The instructions are entirely vague ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') and could apply to literally any topic. Everything is deferred to a resource file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is a rough sequence implied ('Clarify goals' → 'Apply best practices' → 'Validate outcomes' → 'Provide actionable steps'), but these are generic platitudes rather than meaningful workflow steps. No validation checkpoints, no concrete process for working with advanced types.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in theory. However, no bundle files are provided, meaning the referenced file doesn't exist. The SKILL.md itself contains almost no substantive content, making it an empty shell pointing to a nonexistent resource.	2 / 5
	Total	8 / 20 Passed

Description

52%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 a clear domain (TypeScript advanced types) and enumerates specific type system features, providing reasonable keyword coverage. However, it lacks any 'when to use' guidance and frames itself as 'guidance for mastering' rather than describing concrete actions Claude would perform, making it weaker for skill selection purposes.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about TypeScript generics, conditional types, type inference, or needs help writing complex type definitions.'

Replace the vague 'comprehensive guidance for mastering' framing with concrete actions like 'Explains, demonstrates, and helps write advanced TypeScript types including...'

Include additional natural trigger terms like 'type inference', 'type narrowing', 'infer keyword', '.ts files', or 'type errors' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Names the domain (TypeScript's advanced type system) and lists several specific type categories (generics, conditional types, mapped types, template literal types, utility types), but doesn't describe concrete actions—it says 'guidance for mastering' which is vague about what it actually does.	3 / 5
Completeness	Has a somewhat clear 'what' (guidance on TypeScript advanced types) but completely lacks a 'when' clause. There's no explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 3, and since the 'what' is also somewhat vague ('comprehensive guidance for mastering'), it falls to 2.	2 / 5
Trigger Term Quality	Includes good technical keywords users would search for: 'TypeScript', 'generics', 'conditional types', 'mapped types', 'template literal types', 'utility types', 'type-safe'. Missing some natural phrases like 'type inference', 'type narrowing', 'infer keyword', or file extensions like '.ts'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct due to the specific focus on TypeScript's advanced type system features. Could potentially overlap with a general TypeScript skill or a coding best practices skill, but the enumeration of specific type system features (conditional types, mapped types, template literal types) narrows the scope well.	4 / 5
	Total	13 / 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-advanced-types/SKILL.md
Commit: 7520423

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.