CtrlK
BlogDocsLog inGet started
Tessl Logo

typescript-advanced

Advanced TypeScript patterns including generics, conditional types, mapped types, template literals, and type guards

64

Quality

76%

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 ./skills/typescript-advanced/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 lean, well-organized catalog of executable advanced TypeScript patterns with strong conciseness and actionability; its only gap is the absence of a sequenced workflow with validation checkpoints, which is minor for a reference skill.

DimensionReasoningScore

Conciseness

The body is almost entirely executable code under terse section headers with no padding or explanations of concepts Claude already knows (no 'TypeScript is a language that...'), so every token earns its place.

3 / 3

Actionability

Each section provides complete, copy-paste-ready TypeScript (e.g. `function findById<T extends HasId>`, `type ExtractRouteParams<...>`, `function isNonNull<T>(...): value is T`), matching the fully-executable anchor.

3 / 3

Workflow Clarity

This is a patterns reference rather than a sequenced process; the closing Checklist offers some validation guidance but there is no ordered workflow with explicit validate-fix-retry checkpoints, so it lands at 'steps/checklist present but gaps'.

2 / 3

Progressive Disclosure

No external references are needed and none are present, so the clean, well-sectioned headers (Generics, Conditional Types, Mapped Types, etc.) provide easy one-level navigation without nested references.

3 / 3

Total

11

/

12

Passed

Description

65%

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 specific and uses natural TypeScript terminology, but it lists covered topics rather than actions and omits any 'Use when...' trigger guidance, capping completeness at 2.

Suggestions

Reframe the topic list as concrete actions, e.g. 'Write and refactor advanced TypeScript: generics, conditional/mapped types, template literals, and type guards.'

Add an explicit trigger clause such as 'Use when designing complex TypeScript types, debugging type errors, or when the user mentions generics, conditional types, mapped types, or type guards.'

Add common trigger variations ('type errors', 'strict null checks', 'type narrowing') to sharpen distinctiveness from a general TypeScript skill.

DimensionReasoningScore

Specificity

The description names a clear domain ("Advanced TypeScript patterns") and lists five concrete topics ("generics, conditional types, mapped types, template literals, and type guards"), but these are noun-phrase topics rather than concrete actions (no verbs like 'write', 'refactor', 'apply'), so it sits at the 'names domain and some actions' level rather than the verb-driven anchor 3.

2 / 3

Completeness

It answers 'what' (advanced TS patterns and the listed topics) but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms such as "generics", "conditional types", "mapped types", "template literals", and "type guards" are exactly the natural vocabulary TypeScript developers use when asking for help, giving good coverage of keywords a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The "Advanced TypeScript patterns" niche is fairly specific, but with no explicit trigger guidance it could still overlap with a general TypeScript skill, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

9

/

12

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
rohitg00/awesome-claude-code-toolkit
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.