CtrlK
BlogDocsLog inGet started
Tessl Logo

typescript

Apply project conventions for TypeScript types, imports, generics, factories, and runtime schemas. Use when editing `.ts` files or reviewing TypeScript design and tests.

68

Quality

83%

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

78%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-structured, dense conventions reference with concrete code patterns and excellent progressive disclosure via a clearly signaled reference map. Its main weakness is the somewhat verbose Go-to-Definition section, which could be tightened for token efficiency.

Suggestions

Tighten the 'Go-to-Definition Awareness' regression list: each bullet currently leads with prose context before the pattern; lead with the anti-pattern snippet and trim the explanatory preamble.

Consider moving the longest 'Go-to-Definition Awareness' worked examples (e.g. the ManualRecorderLive reference) into a reference file and summarizing the rule inline, reducing body tokens.

DimensionReasoningScore

Conciseness

The rule list is dense and assumes TypeScript competence with no beginner padding, but the 'Go-to-Definition Awareness' section runs long with prose-heavy regression entries that could be tightened, so it is efficient with minor trimming opportunities rather than fully lean.

4 / 5

Actionability

Rules give concrete, executable patterns such as 'Base & Extra', 'ReturnType<typeof createThing>', and 'default: value satisfies never' with named anti-patterns, providing mostly actionable guidance with minor gaps for an instruction-style skill.

4 / 5

Workflow Clarity

This is a conventions/guidelines doc rather than a multi-step destructive workflow, so the destructive-validation cap does not apply; rules are clearly grouped into Core Rules, Go-to-Definition Awareness, and Reference Map with a clear sequence of concerns.

4 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled one-level-deep Reference Map linking to seven real reference files, each described by scope, splitting content appropriately and making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

87%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 concrete, well-triggered, and distinct: it names multiple capability areas and gives explicit 'Use when' guidance tied to `.ts` files. It is among the strongest descriptions, with only minor room to add more user-natural synonyms.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — 'TypeScript types, imports, generics, factories, and runtime schemas' — covering multiple specific actions with only minor gaps in coverage, matching the 'several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Clearly states what it does ('Apply project conventions for TypeScript types, imports, generics, factories, and runtime schemas') and an explicit 'Use when editing `.ts` files or reviewing TypeScript design and tests' trigger, answering both what and when with concrete phrases.

5 / 5

Trigger Term Quality

Natural terms like 'editing `.ts` files' and 'reviewing TypeScript design and tests' plus the `.ts` extension give good keyword coverage, but a few common user phrasings (e.g. 'type errors', 'compile errors') are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to a TypeScript-conventions niche with a file-extension trigger and explicit composition with sibling skills, giving a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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
EpicenterHQ/epicenter
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.