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.

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/javascript-typescript/skills/typescript-advanced-types/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A thorough, well-organized TypeScript reference with strong executable examples and a clean one-level reference split. Its main weakness is verbosity: it re-teaches built-in utilities and basic generics that Claude already knows, inflating the token budget without adding marginal value.

Suggestions

Replace the 'Utility Types' section's per-built-in re-explanations with a compact table or a pointer to references/details.md; Claude already knows Partial/Pick/Omit/Record.

Trim the basic generics primer (identity, HasLength) to a single representative example and move extended coverage to the reference file.

Add a short 'Applying these types' workflow with a validation checkpoint (e.g., compile with --strict and confirm no type errors) to give the conceptual material a procedural spine.

DimensionReasoningScore

Conciseness

Large portions re-explain concepts Claude already knows, including basic generics ('identity', 'HasLength' constraints) and the standard built-in utility types (Partial, Required, Readonly, Pick, Omit, Exclude, Extract, NonNullable, Record) with per-line comments, making it noticeably padded.

2 / 5

Actionability

The body provides abundant executable, copy-paste-ready TypeScript with shown result types (e.g., the Getters, Path, and PickByType examples), with only minor gaps where examples are illustrative rather than task-driven.

4 / 5

Workflow Clarity

There is a logical organization (concepts -> best practices -> pitfalls -> performance) but no procedural sequence or validation checkpoints; this is acceptable for a conceptual reference, yet no explicit workflow is sequenced.

3 / 5

Progressive Disclosure

Content is well-sectioned and offloads advanced patterns to a real, clearly signaled one-level-deep reference ('Detailed sections (starting with ## Advanced Patterns) live in references/details.md'), though the main file still inlines substantial reference material that could be split further.

4 / 5

Total

13

/

20

Passed

Description

70%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 solid, well-structured description that clearly states both capability and explicit use-conditions with good keyword coverage. It leans on topic enumeration over distinct concrete actions and uses task-oriented rather than user-speech-oriented triggers, capping it just short of the top anchors.

Suggestions

Lead the 'what' clause with concrete operations (e.g., 'Build, infer, and transform TypeScript types...') instead of listing type categories.

Add user-utterance-oriented triggers to the 'Use when' clause (e.g., 'or when the user asks about TypeScript type errors, generics, or type inference').

DimensionReasoningScore

Specificity

The description names the domain and lists concrete trigger actions ('implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety') but the 'what' portion largely enumerates type categories (generics, conditional types, mapped types) rather than distinct concrete operations, so it is not comprehensive.

3 / 5

Completeness

It explicitly answers both 'what' ('Master TypeScript's advanced type system including...') and 'when' (an explicit 'Use when...' clause with three concrete triggers), but the triggers are framed as task situations rather than user-utterance phrases, keeping it just below the top anchor.

4 / 5

Trigger Term Quality

Good natural keyword coverage including 'TypeScript', 'generics', 'conditional types', 'type-safe', and 'compile-time type safety' with the synonym pair 'type-safe'/'type safety'; a few common user phrases like 'type errors' or 'type inference' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'TypeScript advanced type system' niche is clearly scoped with distinct triggers, with only minor overlap risk against a hypothetical general-purpose TypeScript skill.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.