typescript

TypeScript project conventions: derived types, type placement, acronym casing, imports, generics, factories, and runtime schema patterns. Use when editing `.ts` files, defining exported types, reviewing type names, or organizing type tests.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/typescript/SKILL.md

Quality

Content

72%

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

The body is a high-quality conventions skill: highly actionable rules with concrete code tokens and a well-structured reference map pointing to real, one-level-deep files. Its weaker points are the verbosity of the Go-to-Definition section and the absence of any workflow sequencing or validation checkpoints.

Suggestions

Tighten the 'Go-to-Definition Awareness' bullets to lead with the pattern and keep rationale to one clause, cutting length without dropping the concrete code examples.

If a natural multi-step workflow exists (e.g., 'add a new exported type'), surface it as a short numbered checklist so the conventions have an application sequence.

Dimension	Reasoning	Score
Conciseness	The body is dense with novel project-specific conventions and avoids explaining concepts Claude already knows, but the 'Go-to-Definition Awareness' section is wordy across eight detailed bullets and could be tightened without losing clarity.	2 / 3
Actionability	Rules are concrete and executable with specific code tokens ('Use `type`, not `interface`', 'ReturnType<typeof createThing>', 'Base & Extra') and the Go-to-Def section pairs each regression with a concrete code example, giving copy-paste-ready guidance.	3 / 3
Workflow Clarity	Conventions are grouped into 'Core Rules' and 'Go-to-Definition Awareness' sections, but it is a flat rule list with no multi-step sequencing or validation checkpoints, which fits the 'structure present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	The 'Reference Map' cleanly signals seven one-level-deep reference files, each annotated with its contents, and all seven referenced files exist under references/, giving clear overview-to-detail navigation.	3 / 3
	Total	10 / 12 Passed

Description

82%

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 well-structured with an explicit 'Use when' trigger clause and good natural keyword coverage, clearly answering both what and when. Its main weakness is that capabilities are listed as topic nouns rather than concrete action verbs, and the broad TS scope risks overlap with the narrower sibling skills it composes with.

Suggestions

Reframe the capability list around concrete actions (e.g., 'derive or import types, place types in types.ts, name factories, organize barrels') instead of topic nouns to lift specificity.

Tighten the trigger clause to differentiate from sibling skills — e.g., note that arktype/typebox schema details or testing setup belong to those narrower skills.

Dimension	Reasoning	Score
Specificity	Names a clear domain plus seven concrete topic areas ('derived types, type placement, acronym casing, imports, generics, factories, and runtime schema patterns'), but these are framed as topic nouns rather than concrete action verbs, so it does not reach the 'multiple specific concrete actions' anchor.	2 / 3
Completeness	It explicitly states what it does ('TypeScript project conventions: ...') and when to use it ('Use when editing `.ts` files, ...'), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	The 'Use when' clause supplies natural terms a developer would actually say — 'editing `.ts` files, defining exported types, reviewing type names, or organizing type tests' — giving good coverage comparable to the level-3 example.	3 / 3
Distinctiveness Conflict Risk	The TS-general triggers ('editing `.ts` files') are specific enough to avoid most non-TS skills, but the skill composes with narrower siblings (arktype, typebox, testing) mentioned in the body, so overlap with those similar skills remains possible.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EpicenterHQ/epicenter
Path: .agents/skills/typescript/SKILL.md
Commit: cb12bcc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.