typescript-advanced-types

Comprehensive guidance for mastering TypeScript's advanced type system including generics, conditional types, mapped types, template literal types, and utility types for building robust, type-safe applications.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/typescript-advanced-types/SKILL.md

The canonical home for this skill is typescript-advanced-types in rmyndharis/antigravity-skills

Quality

Content

57%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 concise and well-structured but offers only vague, abstract instructions with no inline executable guidance, and its single external reference points to a file that is missing from the bundle.

Suggestions

Add at least one concrete inline TypeScript example (e.g., a mapped or conditional type snippet) so the skill is actionable without opening the external file.

Either create 'resources/implementation-playbook.md' or remove/fix the broken reference so progressive disclosure resolves correctly.

Tighten the Instructions into a concrete sequenced workflow with explicit validation checkpoints rather than generic directives like 'Apply relevant best practices'.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — short bullet lists with no padding and no explanation of TypeScript or type concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	The Instructions are high-level abstractions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') with no concrete code, commands, or specific TypeScript patterns inline; specifics are deferred to a referenced file, leaving only minimal concrete guidance.	2 / 5
Workflow Clarity	A rough sequence is present (clarify → apply best practices → verify) and validation is mentioned ('validate outcomes', 'verification'), but there are no explicit checkpoints or feedback loops, fitting 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Sections are well organized (Use when / Do not use / Instructions / Resources) and reference a single one-level-deep file, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle, so the reference does not resolve — more than a minor organization gap.	3 / 5
	Total	13 / 20 Passed

Description

61%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 clearly identifies a focused niche and lists relevant TypeScript type-system terms, but it lacks an explicit 'Use when...' trigger clause and frames capabilities as topics rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger scenarios (e.g., 'Use when designing generic utilities, conditional type logic, or type-safe API contracts').

Reframe the topic list as concrete actions (e.g., 'Design generic components, write conditional and mapped types, derive template literal types') instead of noun phrases.

Include natural synonyms users say, such as 'type inference' and 'type-level programming', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates concrete domain elements ('generics, conditional types, mapped types, template literal types, and utility types') but as topics rather than actions; the only verbs ('mastering', 'building') are generic, so it sits at the 'names domain and 1-2 concrete actions but not comprehensive' level rather than listing several specific actions.	3 / 5
Completeness	Provides a clear 'what' ('Comprehensive guidance for mastering TypeScript's advanced type system including...') but includes no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains natural terms a TypeScript user would say ('advanced type system', 'generics', 'conditional types', 'mapped types', 'template literal types', 'utility types') with good synonym coverage, but misses common variants like 'type inference' or 'type-level programming' that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Targets a specific niche (advanced TypeScript types) with distinct triggers and only minor overlap risk with general TypeScript/coding skills; the broad 'building robust, type-safe applications' phrasing keeps it from a 5.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/typescript-advanced-types/SKILL.md
Commit: debb2ec

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