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

65%

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

46%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 body is a comprehensive, code-rich TypeScript reference with strong actionability but poor token efficiency and no progressive disclosure — it re-teaches material Claude already knows and crams everything into one monolithic file. It works as a tutorial but not as a well-structured skill.

Suggestions

Move the six Advanced Patterns, the utility-types reference, Type Testing, and Common Pitfalls into separate reference files (e.g. PATTERNS.md, REFERENCE.md) and keep SKILL.md as a concise overview with one-level-deep links, fixing progressive_disclosure and cutting conciseness bloat.

Delete material Claude already knows — the built-in utility-types catalog and basic generics/conditional-types primers — and keep only non-obvious patterns, reducing the ~710 lines substantially.

Remove the redundant opening line that restates the frontmatter description, since it adds tokens without new information.

Dimension	Reasoning	Score
Conciseness	The 710-line body re-teaches concepts Claude already knows (built-in utility types like Partial/Pick/Omit, basic generics, type guards) and opens by restating the description, making it noticeably verbose; it avoids a 1 only because the content is code-heavy rather than prose padding.	2 / 5
Actionability	Provides abundant concrete, syntactically valid, copy-paste TypeScript examples across every section, with only minor gaps such as the "// Implementation here" placeholder and "return {} as any" in the API client pattern.	4 / 5
Workflow Clarity	This is a topical reference rather than a sequenced workflow, so it has clear section organization but no multi-step process or validation checkpoints; the simple-skill exception does not apply since it is a broad multi-topic reference.	3 / 5
Progressive Disclosure	All content is inlined into a single ~710-line SKILL.md with no external references; the six advanced patterns, the full utility-types reference, type testing, and pitfalls clearly belong in separate files, matching anchor-2's inlined-content failure despite the presence of section headers.	2 / 5
	Total	11 / 20 Passed

Description

83%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 strong: it explicitly covers both what the skill does and when to use it, with a clear niche and good trigger terms. It loses points only for slightly abstract action verbs and a couple of broad triggers that create minor overlap risk.

Dimension	Reasoning	Score
Specificity	Lists five concrete type constructs ("generics, conditional types, mapped types, template literals, and utility types") giving strong coverage, but the verbs ("Master", "implementing complex type logic") are more abstract than anchor-5's concrete actions, so it sits above 3 yet below 5.	4 / 5
Completeness	Explicitly states both the "what" (mastering the advanced type system) and the "when" ("Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety"), matching the anchor-5 example structure with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a TS user would say ("generics", "conditional types", "mapped types", "type-safe", "compile-time type safety"), but lacks synonyms and file extensions (e.g. ".ts", "type inference") that would push it to anchor 5.	4 / 5
Distinctiveness Conflict Risk	The "advanced types" niche is mostly distinct, but the trigger "ensuring compile-time type safety in TypeScript projects" is broad enough to overlap a general TypeScript skill, keeping it just below anchor 5.	4 / 5
	Total	17 / 20 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: d76efae

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