CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript

Apply project conventions for TypeScript types, imports, generics, factories, and runtime schemas. Use when editing `.ts` files or reviewing TypeScript design and tests, including constraints that need to name an invalid literal key or string in a compiler error.

Quality

84%

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.

A well-crafted conventions skill: high-signal project-specific rules, concrete inline code patterns, and exemplary progressive disclosure with a verified, accurately described reference bundle. The main weaknesses are mild — a few overloaded run-on bullets and the absence of any decision ordering or priority among the flat rule list.

Suggestions

Split the longest run-on rules (the read-methods bullet and the `satisfies`-generic bullets) into shorter statements or move the extended rationale into their linked reference files to tighten conciseness.

Add a brief prioritization note (e.g., which rules are hard constraints vs. defaults, or which to check first when editing an existing file) so the flat Core Rules list doubles as a lightweight workflow.

Convert abstract directives like "New named types must earn their place" into a one-line decision test or a do/don't example pair to raise actionability.

DimensionReasoningScore

Conciseness

The body is dense with project-specific, non-inferable rules (per-package `.ts`/`.js` import extensions, ADR-0769, `#platform/*` splits, specific package names) and explains nothing Claude already knows. A handful of run-on bullets — notably the read-methods rule and the noisy-`satisfies` rules — carry nested clauses that could be trimmed, placing it just below the every-token-earns-its-place level.

4 / 5

Actionability

Concrete, adaptable patterns appear throughout: `createMailbox({ db })`, `Base & Extra` vs `Omit<Base, 'k'> & { k: U }`, `ReturnType<typeof createThing>`, `export type CapturesHarness = Awaited<ReturnType<typeof openCaptures>>`, and `default: value satisfies never`. It stops short of fully copy-paste-ready coverage because several rules are abstract directives ("New named types must earn their place", "Treat local shape copies as boundary smells").

4 / 5

Workflow Clarity

As a conventions skill rather than a multi-step process, it has no validation checkpoints to include and no destructive/batch operations that would cap the score. Content is organized into clear sections (Core Rules, Go-to-Definition Awareness, Reference Map) with per-reference "read when" guidance, but the rules form a flat list with no ordering or priority guidance for when rules interact.

4 / 5

Progressive Disclosure

The ~60-line body is a clean overview split into three well-labeled sections, with eight one-level-deep reference files that all exist and whose contents match their one-line descriptions in the Reference Map. Inline links to `references/project-conventions.md` and `references/factory-patterns.md` point to real files, and navigation is easy — a clear match for the top anchor.

5 / 5

Total

17

/

20

Passed

Description

83%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 strong description: it explicitly states what the skill does and when to use it, with concrete triggers tied to file extensions and tasks. Keyword coverage is good though it lacks a few common synonyms (TS, .tsx), and the single governing verb "Apply project conventions" keeps the action enumeration slightly below comprehensive.

DimensionReasoningScore

Specificity

The description names the TypeScript domain plus five concrete capability areas ("types, imports, generics, factories, and runtime schemas") and two actions ("Apply project conventions" and "reviewing TypeScript design and tests"). It lists several specific areas with minor gaps rather than the multiple distinct, comprehensive actions of a 5.

4 / 5

Completeness

Both what ("Apply project conventions for TypeScript types, imports, generics, factories, and runtime schemas") and when ("Use when editing `.ts` files or reviewing TypeScript design and tests") are explicitly stated, with an additional concrete trigger for compiler-error constraint cases. This clearly matches the anchor for explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "TypeScript", "editing `.ts` files", "reviewing TypeScript design and tests", "types", "imports", "generics". A few natural variations are missing (e.g., "TS", ".tsx"), keeping it just below the comprehensive synonym/extension coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (project TypeScript conventions) distinct from other-language or general skills, with mostly-distinct triggers. Minor overlap risk remains with closely related skills such as testing or schema-library skills, which the body acknowledges compose with it.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/typescript/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.