CtrlK
BlogDocsLog inGet started
Tessl Logo

typescript-best-practices

Write idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A lean, well-organized best-practices reference whose body is token-efficient and clearly structured, but it lacks inline executable examples and its progressive disclosure is incomplete — one bundle file is orphaned and another contains broken nested references.

Suggestions

Add a few inline copy-paste-ready code examples for the highest-value patterns (e.g., async/await with Promise.all and catch-as-unknown narrowing) instead of offloading all examples to references/examples.md, so the body is directly actionable.

Link references/REFERENCE.md from the body's References section — it currently exists in the bundle but is not discoverable from SKILL.md.

Fix or remove the broken links in REFERENCE.md to project-structure.md and configuration.md (these files do not exist); either create them or inline their content to avoid 2-level-deep dead references.

DimensionReasoningScore

Conciseness

The body is a dense bullet list of directives with no padding and no explanations of concepts Claude already knows (it assumes familiarity with async/await, PascalCase, etc.), so every token earns its place.

3 / 3

Actionability

Guidance is concrete and specific (names Promise.all, ?., ??, import type, jest.Mocked<T>, eslint-plugin-import, Zod), but the body contains no inline executable code examples — all copy-paste-ready examples are deferred to references/examples.md, falling short of the 3 anchor's "specific examples; copy-paste ready" bar.

2 / 3

Workflow Clarity

This is a sub-50-line, single-purpose best-practices reference with no multi-step or destructive operation requiring validation checkpoints; per the simple-skills note, its clear, well-organized sectioning (Implementation Guidelines, Anti-Patterns, References) warrants the top score.

3 / 3

Progressive Disclosure

The body well-signals one reference (examples.md, which exists), but references/REFERENCE.md is an orphaned bundle file never linked from the body, and REFERENCE.md itself contains broken links to missing files (project-structure.md, configuration.md), so the structure is only partially organized.

2 / 3

Total

10

/

12

Passed

Description

90%

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 description with explicit what/when structure and natural trigger terms; its only weakness is mild buzzword fluff ("clean, maintainable code", "patterns") in the action statement that keeps specificity below the top anchor.

DimensionReasoningScore

Specificity

The description names the domain (TypeScript) and a couple of actions ("Write", "refactoring"), but the core action "Write idiomatic TypeScript patterns for clean, maintainable code" leans on abstract fluff ("patterns", "clean, maintainable code") rather than listing multiple concrete actions, so it does not reach the multi-action bar of a 3.

2 / 3

Completeness

It clearly answers both what ("Write idiomatic TypeScript patterns...") and when via an explicit "Use when writing or refactoring TypeScript classes, functions, modules, or async logic" clause, satisfying the explicit-trigger requirement that would otherwise cap at 2.

3 / 3

Trigger Term Quality

Natural user terms are well covered — "TypeScript", "classes", "functions", "modules", and "async logic" are all phrasings a user would actually say when needing this skill, matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The TypeScript-scoped framing ("TypeScript classes, functions, modules, or async logic") carves a clear niche with distinct triggers, making it unlikely to fire for non-TypeScript skills despite classes/functions being generic terms.

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.