CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-best-practices

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

61

Quality

77%

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 ./.github/skills/typescript/typescript-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A compact, well-sectioned style-guide skill that names specific tools and rules rather than teaching basics, but it demonstrates none of its patterns inline and leaves one of its two bundle files unlinked. The stray 'Priority: P1' heading and 'Canonical response anchors' tail add confusion without guidance.

Suggestions

Add one-line inline code snippets for the highest-value patterns (e.g., a never-based exhaustiveness check, a typed catch-and-narrow block) instead of deferring every example to references/examples.md.

Delete the empty '## **Priority: P1 (HIGH)**' heading and either expand or remove the 'Canonical response anchors' section, since neither tells Claude what to do.

Link references/REFERENCE.md from the References section alongside examples.md so the whole bundle is navigable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean bullet guidance with no explanations of concepts Claude already knows, but contains trimmable noise: the empty '## **Priority: P1 (HIGH)**' heading, the 'No Default Exports' anti-pattern duplicating the Modules bullet, and the cryptic 'Canonical response anchors' section that adds little value.

4 / 5

Actionability

Some rules are concrete and tool-named ('Enforce ... via eslint-plugin-import', 'Use Zod or Tsoa', 'Enable noUnusedLocals', 'jest.Mocked<T>'), but the body contains no code examples at all and several directives stay abstract ('Favor composition over inheritance and dependency injection'), deferring all demonstrations to references/examples.md.

3 / 5

Workflow Clarity

As a simple single-purpose skill under 50 lines, the sections (Implementation Guidelines, Anti-Patterns, References) are clear and well-organized, but the empty 'Priority: P1 (HIGH)' heading with no content beneath it is a minor clarity gap.

4 / 5

Progressive Disclosure

The body clearly signals a one-level-deep reference to references/examples.md with a summary of its contents, but the bundle's references/REFERENCE.md is orphaned — never linked from SKILL.md — leaving navigation incomplete.

4 / 5

Total

15

/

20

Passed

Description

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

A solid description that clearly states both capability and explicit trigger conditions in third-person imperative voice. Its main weakness is thin action specificity — 'write idiomatic patterns for clean, maintainable code' leans on buzzwords — and missing file-extension triggers.

DimensionReasoningScore

Specificity

It names the TypeScript domain with two actions ('Write idiomatic TypeScript patterns', 'refactoring') applied to concrete targets, but 'clean, maintainable code' is fluffy and only 1-2 real actions are listed — matching the 1-2-concrete-actions anchor rather than the several-specific-actions anchor.

3 / 5

Completeness

It explicitly answers both what ('Write idiomatic TypeScript patterns for clean, maintainable code') and when ('Use when writing or refactoring TypeScript classes, functions, modules, or async logic') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are present ('TypeScript', 'refactoring', 'classes, functions, modules, or async logic'), but common variations like '.ts', '.tsx', and 'type safety' are missing.

4 / 5

Distinctiveness Conflict Risk

It is scoped to TypeScript with distinct triggers, but the generic programming nouns 'classes, functions, modules' create minor overlap risk with general code-style skills.

4 / 5

Total

16

/

20

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.

Validation — 14 / 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

Path

.github/skills/typescript/typescript-best-practices/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.