CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/typescript-advanced

Comprehensive TypeScript guidance covering compiler configuration, advanced types, utility types, type guards, strict mode workflows, and documentation patterns; use when configuring tsconfig, designing complex generics, making illegal states unrepresentable, fixing type errors, or writing testable and maintainable type-safe APIs.

66

Quality

83%

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

Overview
Quality
Evals
Security
Files

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured navigation hub with executable commands, explicit validation-driven workflows, and clean BAD/GOOD examples. Its weak points are duplicated trigger sections that re-teach basics and reference paths that point to bundled files which are absent from the skill bundle.

Suggestions

Remove the redundant "Use When" section (the description and "When to Apply" already cover triggers) and trim the Quick Fixes explanatory text to just the BAD/GOOD code, since Claude already understands these compile-error causes.

Either create the missing files under references/ (compiler-strict-mode.md, practices-type-first.md, types-advanced-conditional.md, utilities-builtin-partial.md, narrowing-guards.md, docs-jsdoc-patterns.md) or remove the broken reference citations so navigation resolves to real content.

In the How to Use block, the file listing overlaps with the Navigation Workflow citations — consolidate them into one authoritative reference list to avoid drift between the two.

DimensionReasoningScore

Conciseness

The body is mostly lean (quick commands, BAD/GOOD pairs), but the "When to Apply" and "Use When" sections overlap heavily, and the Quick Fixes section re-explains basic TS error causes Claude already knows, adding unnecessary tokens.

2 / 3

Actionability

It provides fully executable commands (e.g. `npx tsc --noEmit`, `npx typedoc --out docs src/index.ts`, `rg -n "\bany\b|@ts-ignore| as " src`) and complete, copy-paste-ready BAD/GOOD TypeScript code examples rather than pseudocode.

3 / 3

Workflow Clarity

The Navigation Workflow is a clearly numbered sequence with explicit validation checkpoints — each step runs `npx tsc --noEmit` and references a file on error, giving a validate-then-fix feedback loop rather than implicit checkpoints.

3 / 3

Progressive Disclosure

The hub design is well-organized with one-level-deep, clearly signaled references and a category table, but the cited reference files (e.g. references/compiler-strict-mode.md, references/narrowing-guards.md) do not exist in any bundled references/ directory, so the navigation points to missing material.

2 / 3

Total

10

/

12

Passed

Description

85%Weight 40%Scale 1-3

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, well-structured description that covers capabilities, explicit use-when triggers, and a distinct niche. Its main weakness is trigger phrasing that leans toward developer-design jargon rather than natural user language.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability domains — "compiler configuration, advanced types, utility types, type guards, strict mode workflows, and documentation patterns" — matching the multiple-specific-actions anchor rather than the names-domain-and-some-actions level.

3 / 3

Completeness

It explicitly answers both what ("Comprehensive TypeScript guidance covering...") and when ("use when configuring tsconfig, designing complex generics, fixing type errors..."), with an explicit Use-when clause rather than an implied one.

3 / 3

Trigger Term Quality

It lists relevant triggers like "configuring tsconfig", "designing complex generics", and "fixing type errors", but several phrases (e.g. "making illegal states unrepresentable") are design jargon a typical user would not naturally say, so coverage is good rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The advanced-TypeScript niche with specific triggers (tsconfig, generics, type guards, strict mode) is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents