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.

1.02x

Quality

75%

Does it follow best practices?

Impact

82%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/typescript-advanced-types/SKILL.md

The canonical home for this skill is typescript-advanced-types in wshobson/agents

Quality

Content

50%

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

The body is a thorough, executable TypeScript reference, but it is far too verbose — re-teaching built-in utilities and basic generics Claude already knows — and monolithically inline with no progressive disclosure to reference files. Actionability is strong; conciseness and disclosure are weak.

Suggestions

Strip the "Core Concepts" basics (identity generics, built-in Partial/Readonly/Pick/Omit/etc.) that Claude already knows; keep only the non-obvious advanced patterns and type-testing techniques to cut the body to a lean overview.

Move the six "Advanced Patterns" and the type-testing/pitfalls material into reference files (e.g. references/patterns.md, references/type-testing.md) and link to them one level deep from SKILL.md, so the main file is an overview that practices progressive disclosure.

Add a short "When to Use This Skill"-driven workflow that maps a user request (e.g. "make this API type-safe") to a concrete sequence of steps, rather than only presenting a catalog of type techniques.

Dimension	Reasoning	Score
Conciseness	The ~710-line body re-explains concepts Claude already knows (basic generics, the identity function, and built-in utility types Partial/Required/Readonly/Pick/Omit/Exclude/Extract/NonNullable/Record with inline tutorials), padded with "Purpose" prose and elementary examples. Not a 2 because the verbosity is pervasive rather than a few tighten-able spots — it reads like a textbook, not skill guidance.	1 / 3
Actionability	Provides numerous complete, executable TypeScript code blocks (typed event emitter, API client, builder, form validator, reducer) that are largely copy-paste ready. Not a 2 because the examples are real runnable code with concrete types, not pseudocode, despite a couple of stub markers ("// Implementation here").	3 / 3
Workflow Clarity	Content is organized into sections ("When to Use", "Core Concepts", "Advanced Patterns") with best-practices and pitfall lists, but there is no sequenced multi-step process or validation checkpoints for actually applying these types to a task. Not a 3 because no workflow with feedback/validation steps is present; not a 1 because the material is at least clearly structured rather than disordered.	2 / 3
Progressive Disclosure	All ~710 lines sit inline in SKILL.md with no reference files (no references/scripts/assets exist), so content that clearly belongs in separate files (the six advanced patterns, the type-testing section) is not split out. Not a 3 because it is monolithic with no one-level-deep references; not a 1 because headers do provide discoverable structure rather than an undifferentiated wall.	2 / 3
	Total	8 / 12 Passed

Description

100%

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 explicitly covers both what the skill does and when to use it, with strong natural trigger terms. It is a model of the rubric's good examples.

Dimension	Reasoning	Score
Specificity	Names specific concrete capabilities ("generics, conditional types, mapped types, template literals, and utility types") and concrete actions ("implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety"). Not the level below, which only names a domain and some actions without this breadth.	3 / 3
Completeness	Explicitly answers both what ("Master TypeScript's advanced type system...") and when via an explicit "Use when..." clause listing triggering situations. Not a 2 because the trigger guidance is explicit, not merely implied.	3 / 3
Trigger Term Quality	Covers natural terms a TypeScript developer would actually say — "TypeScript", "generics", "conditional types", "mapped types", "type-safe", "compile-time type safety" — with good variation. Not a 2 because it goes well beyond a single keyword to include common phrasings users invoke.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (advanced TypeScript type system) with distinct triggers unlikely to fire for unrelated skills. Not a 2 because the scope is narrowly scoped to advanced type logic rather than overlapping with general TypeScript or coding skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (718 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/typescript-advanced-types/SKILL.md
Commit: 45116fd

Reviewed: about 13 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.