CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

1.02x
Quality

66%

Does it follow best practices?

Impact

82%

1.02x

Average score across 3 eval scenarios

SecuritybySnyk

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

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-formatted but monolithic TypeScript tutorial that spends most of its tokens restating standard TypeScript knowledge Claude already has, with genuinely useful advanced patterns buried inside. Restructuring into lean core guidance plus references files, and adding type-test verification commands, would raise quality substantially.

Suggestions

Cut or move the basic-generics, built-in utility-type, and type-guard sections into a references/ file (or drop them entirely — Claude already knows Partial/Pick/Omit semantics) and keep SKILL.md to non-obvious advanced patterns and decision guidance.

Add a short decision guide mapping each 'When to Use' bullet to the specific pattern that solves it, so the reference functions as a workflow rather than a topic catalog.

Include an executable type-test command (e.g., tsd or tsc expect-error snippets) alongside the AssertEqual examples so the 'Test your types' best practice has a real verification loop, and complete the APIClient stub implementation.

DimensionReasoningScore

Conciseness

The ~717-line body extensively re-explains concepts Claude already knows — basic identity generics, from-scratch reimplementations of Partial/Readonly, the full built-in utility-type catalog, and basic type guards — duplicating the TypeScript handbook rather than adding non-obvious knowledge.

2 / 5

Actionability

Examples are concrete, syntactically valid TypeScript covering real patterns (typed event emitter, discriminated unions, form validator), but a few are incomplete: APIClient.request is a stub with '// Implementation here' and 'return {} as any', and Builder.set relies on 'as any' casts.

4 / 5

Workflow Clarity

There is no workflow to sequence: the body is a topic-organized reference with no decision guidance for choosing among patterns and no validation or verification loop (the type-testing section shows an AssertEqual helper but no harness or command for running it).

3 / 5

Progressive Disclosure

Section headers give reasonable structure, but all ~16.8KB lives inline in one monolithic SKILL.md with no bundle files; the pattern library and utility-type catalog clearly belong in one-level-deep references/ files.

3 / 5

Total

12

/

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.

A strong description that clearly states both capability and trigger guidance with concrete, natural keywords. The main gap is that it reads slightly as a topic catalog rather than an action list, and a few natural synonyms (e.g., 'type inference') are absent.

DimensionReasoningScore

Specificity

Enumerates five concrete capability areas ('generics, conditional types, mapped types, template literals, and utility types'), giving several specific items, though these are topic names rather than actions and coverage of advanced inference techniques is only implied.

4 / 5

Completeness

Explicitly answers both what ('Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types') and when ('Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Contains good natural keywords users would actually say — 'TypeScript', 'generics', 'type-safe', 'compile-time type safety', 'type utilities' — but misses common variations such as 'type inference' and the 'TS' shorthand.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers ('conditional types', 'mapped types') unlikely to fire for unrelated skills; minor overlap risk remains with a general-purpose TypeScript skill.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (718 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
udecode/plate
Reviewed

Table of Contents

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.