CtrlK
BlogDocsLog inGet started
Tessl Logo

typescript-pro

Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is well-organized and uses progressive disclosure effectively with verified reference files, but its workflow and main-body guidance stay abstract — there is no executable code and no explicit validation feedback loop in the workflow.

Suggestions

Add a small executable snippet or copy-paste example in the body (e.g. a minimal branded type or discriminated union) so the skill is actionable before loading a reference file.

Insert an explicit validation/feedback checkpoint into the Core Workflow (e.g. 'Run tsc --noEmit; if type errors, fix and re-run before proceeding') to satisfy the verify→fix→retry expectation.

Drop the trailing 'Knowledge Reference' keyword line, which duplicates the frontmatter triggers and the 'When to Use' list without adding guidance.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, assumes Claude's competence (no explanation of what TypeScript is), and every section earns its place; the only mild redundancy is the trailing keyword line which is too minor to drop the score.

3 / 3

Actionability

Concrete directives exist ('use `satisfies`', 'prefer const objects with `as const`', 'enable strict mode') and a load-when reference table, but the body contains no executable code or copy-paste examples — guidance is partly abstract and depends on the reference files.

2 / 3

Workflow Clarity

The 'Core Workflow' lists a clear 5-step sequence, but validation checkpoints are only implicit (the 'Test types' step lacks a verify/fix/retry loop), capping this at the 'steps listed but checkpoints missing' anchor.

2 / 3

Progressive Disclosure

A concise overview points to five real, one-level-deep reference files (all verified present in ./references/) via a well-signaled load-when table, giving clear navigation with no nested-reference indirection.

3 / 3

Total

10

/

12

Passed

Description

100%

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 concise, specific, and complete, with explicit trigger clauses and a well-defined niche. It mirrors the structure of the rubric's good examples and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'type guards, utility types, tRPC integration, monorepo setup' alongside 'advanced type systems, generics, or full-stack type safety', matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (building TS apps with advanced type systems, type guards, tRPC, monorepo setup) and 'when' via 'Use when building TypeScript applications requiring...' and 'Invoke for...', matching the highest anchor.

3 / 3

Trigger Term Quality

Includes natural terms users would say — TypeScript, generics, type safety, tRPC, monorepo, type guards — giving good coverage rather than just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (advanced TypeScript type systems, full-stack type safety via tRPC, monorepo setup) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
zebbern/claude-code-guide
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.