CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-best-practices

Enforces TypeScript best practices and modern patterns

Quality

71%

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 ./packages/core/src/eval/__tests__/fixtures/good-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a well-organized, concise single-purpose skill with executable examples and concrete rules, scoring near the top of the scale. The only minor weakness is slight redundancy between the "When to Use" and "Triggers" sections.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the "When to Use" and "Triggers" sections partially overlap (both describe activation on .ts/.tsx edits), which is minor trimming that could be tightened, matching score 4 rather than a fully lean 5.

4 / 5

Actionability

Rules are concrete directives ("Always use `const`", "Never use `any` — use `unknown` instead") and the examples are complete, executable TypeScript (an exported function with an explicit return type and a discriminated union), copy-paste ready and covering common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

This is a simple single-purpose enforcement skill with no destructive or batch operations, so the validation cap does not apply; the When-to-Use → Rules → Examples → Boundaries flow makes the single action unambiguous, qualifying for the simple-skill score-5 exception.

5 / 5

Progressive Disclosure

The skill is under 50 lines, requires no external references (none exist in the bundle), and is organized into clearly labeled sections (When to Use, Triggers, Rules, Examples, Boundaries), satisfying the guideline that such skills can score 5 on progressive disclosure with good organization.

5 / 5

Total

19

/

20

Passed

Description

37%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 concise and names its domain but lacks concrete actions, natural trigger terms, and any explicit "Use when" guidance, leaving it vague about when the skill should activate. It sits at the lower-middle of the scale and would benefit substantially from a trigger clause and specific capabilities.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers, e.g. "Use when writing or reviewing TypeScript (.ts/.tsx) files, converting JavaScript to TypeScript, or applying linting/quality rules."

Replace the generic verb "Enforces" with 2-3 concrete actions, e.g. "Applies const-over-let, explicit return types, interface-over-type, and unknown-over-any rules to TypeScript code."

Include natural trigger terms and file extensions (TypeScript, .ts, .tsx, type checking, refactoring JS to TS) so users' phrasing matches the description.

DimensionReasoningScore

Specificity

The phrase "Enforces TypeScript best practices and modern patterns" names the domain but the only action verb ("Enforces") is generic, matching the score-2 anchor "Names the domain but actions are minimal or generic"; it does not list 1-2 concrete actions as required for a 3.

2 / 5

Completeness

A clear "what" is present (enforcing TS best practices) but no "when"/"Use when" clause exists, matching the score-3 anchor and respecting the guideline that a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

"TypeScript best practices" and "modern patterns" are one or two generic keywords with no natural user phrases or file extensions like `.ts`/`.tsx`, matching the score-2 anchor and falling short of the relevant-keyword coverage needed for a 3.

2 / 5

Distinctiveness Conflict Risk

Scoping to TypeScript is somewhat specific, but "best practices and modern patterns" is broad and overlaps with general linting/code-quality skills, matching the score-3 anchor rather than the more distinct score-4.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rohitg00/skillkit

Path

packages/core/src/eval/__tests__/fixtures/good-skill/SKILL.md

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.