typescript-advanced-types

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

Quality

63%

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

Quality

Content

43%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 skill body is concise and well-organized but offers almost no actionable guidance — the instructions are generic abstractions with no concrete type patterns or examples, and the single referenced resource file is missing from the bundle.

Suggestions

Replace the abstract Instructions ('Apply relevant best practices', 'Provide actionable steps and verification') with concrete TypeScript type patterns — e.g., a worked conditional/mapped type example or a reusable utility type snippet Claude can adapt.

Add explicit verification guidance, such as checking that types resolve with `tsc --noEmit` or asserting expected behavior with `expectTypeOf`/type-level tests, instead of the vague 'validate outcomes' line.

Create the missing `resources/implementation-playbook.md` (or fix the path) so the progressive-disclosure reference actually resolves, and have the body point to specific sections (e.g., generics, conditional types) for navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; the only redundancy is the opening line restating the frontmatter description and the near-tautological 'Do not use this skill when' section, which keeps it just below the top anchor.	4 / 5
Actionability	The Instructions are high-level abstractions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no concrete code, commands, type patterns, or examples, matching the anchor 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'; it is not 1 because it does enumerate some scoped guidance.	2 / 5
Workflow Clarity	The Instructions imply a rough sequence (clarify -> apply -> validate -> verify) but steps are poorly defined with no concrete checkpoints, matching the anchor 'Rough sequence present but many gaps; steps poorly defined; validation absent'; 'validate outcomes' is too vague to count as a real checkpoint.	2 / 5
Progressive Disclosure	The body has good section structure and signals a one-level-deep reference to `resources/implementation-playbook.md`, but that referenced file and directory do not exist in the bundle, so the navigation does not actually resolve; this places it at 'Some structure but references not fully realized' rather than 4.	3 / 5
	Total	11 / 20 Passed

Description

82%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.

A well-constructed description that cleanly answers both what the skill does and when to use it, with a distinct, low-conflict niche. The main weakness is specificity: capabilities are stated abstractly rather than as concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates feature areas (generics, conditional types, mapped types, template literals, utility types), but the verbs are abstract ('Master', 'implementing', 'creating', 'ensuring') rather than concrete operational actions, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it does not reach 4 because no specific executable capabilities are listed.	3 / 5
Completeness	It explicitly answers both 'what' (master the advanced type system including listed features) and 'when' ('Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety' clause offers good natural trigger coverage; it falls short of 5 because it leans technical and omits common synonyms and concrete file/extension cues users might say.	4 / 5
Distinctiveness Conflict Risk	The niche is narrowly scoped to TypeScript advanced types with explicit trigger phrasing, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/typescript-advanced-types/SKILL.md
Commit: 3eff4af

Reviewed: 15 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.