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.

63

Quality

74%

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-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is well-structured with excellent progressive disclosure through a verified reference table, but the body itself offers no executable code or validation steps, leaving actionability and workflow clarity at the mid-tier.

Suggestions

Add at least one concrete executable snippet (e.g. a minimal strict tsconfig block or a branded-type/type-guard code example) in the body so Claude has copy-paste-ready guidance without loading a reference.

Insert explicit validation checkpoints into the Core Workflow (e.g. run `tsc --noEmit` and only proceed on a clean type check) to convert the sequence into a true feedback loop.

Trim filler such as "10+ years of experience" and de-duplicate the trigger terms shared between Role Definition and Knowledge Reference to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no explanation of basic TS concepts, but contains mild redundancy (Role Definition and Knowledge Reference restate overlapping triggers) and filler ("10+ years of experience", "senior") that could be trimmed, keeping it just below the lean 5.

4 / 5

Actionability

Guidance is given as high-level directives ("Enable strict mode", "Use type-first API design", "Create discriminated unions") with no executable code, tsconfig snippets, or commands in the body — concrete specifics are deferred to references, leaving it incomplete per the anchor that requires concrete code/commands for a 4.

3 / 5

Workflow Clarity

A clear 5-step Core Workflow is sequenced, but it lacks explicit validation checkpoints and feedback loops for operations like build optimization and declaration generation; the absence of validation caps this at 3.

3 / 5

Progressive Disclosure

The body is a clean overview with a Reference Guide table mapping each topic to a real, verified one-level-deep bundle file (advanced-types.md, type-guards.md, utility-types.md, configuration.md, patterns.md) with explicit "Load When" navigation cues, matching the top anchor.

5 / 5

Total

15

/

20

Passed

Description

83%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 is strong: it states concrete capabilities and provides explicit dual trigger phrasing ("Use when" / "Invoke for"), answering both what and when. It is concise, third-person, and largely free of fluff.

DimensionReasoningScore

Specificity

Lists several specific capability areas ("advanced type systems, generics... full-stack type safety", "type guards, utility types, tRPC integration, monorepo setup"), but these read as capability domains rather than concrete verb-driven actions, leaving minor coverage gaps short of a comprehensive 5.

4 / 5

Completeness

Explicitly answers both what ("building TypeScript applications requiring advanced type systems, generics, or full-stack type safety") and when ("Use when building..."; "Invoke for type guards, utility types, tRPC integration, monorepo setup") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user-facing terms like "TypeScript, generics, type safety, tRPC, tsconfig, type guards, discriminated unions" with good coverage, but leans technical and misses common synonyms/variants (e.g. "TS"), falling just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear advanced-TypeScript niche with distinct triggers and low conflict risk, but the broad "TypeScript" framing leaves minor overlap risk with general TS skills, so it sits just below the maximal-distinctiveness anchor.

4 / 5

Total

17

/

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