CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tsconfig

TypeScript config conventions for this monorepo: the two-base layering, the seven leaf tiers, and the never-redeclare list. Use when adding a package, editing any tsconfig.json, picking a tier for a new app, or debugging module resolution.

Quality

91%

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

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

Excellent, dense reference skill: terse tables and complete copy-paste configs make it fully actionable, and it never explains what Claude already knows. The only weaknesses are the missing fix-and-retry loop around `bun typecheck` and a purely single-file structure with no separate reference material.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's TypeScript competence, citing TS 5.0/5.4 defaults and option semantics without explaining basics; every rule, table, and example earns its place with no padding.

5 / 5

Actionability

Guidance is fully executable: complete copy-paste JSONC for both canonical library shapes, exact `extends` values and added options per tier in the table, and exact commands (`bun install`, `bun typecheck`, the git recovery command).

5 / 5

Workflow Clarity

The 'Adding a new package' sequence is clearly ordered with a `bun typecheck` validation checkpoint, but there is no error-recovery guidance for what to do when typecheck fails, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist; the single-file body is well-sectioned and self-contained with one clear one-level pointer (git history recovery for the deleted spec). It is good structure with minor gaps — over 50 lines with no overview-to-detail split — fitting anchor 4 rather than 5.

4 / 5

Total

18

/

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.

A strong description: it states the skill's scope concretely, includes an explicit 'Use when...' clause with natural trigger terms and the exact tsconfig.json filename, and is tightly scoped to the monorepo. Only minor gaps in action phrasing and synonym coverage keep specificity and trigger_term_quality at 4.

DimensionReasoningScore

Specificity

Names the domain and several concrete content areas ('the two-base layering, the seven leaf tiers, and the never-redeclare list'), which is specific but an inventory of topics rather than multiple concrete actions, so it falls just short of the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both what ('TypeScript config conventions for this monorepo: the two-base layering, the seven leaf tiers, and the never-redeclare list') and when ('Use when adding a package, editing any tsconfig.json, picking a tier for a new app, or debugging module resolution') with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Triggers like 'editing any tsconfig.json', 'adding a package', and 'debugging module resolution' are natural user phrasings including the exact filename, but common synonyms such as 'compiler options' or 'TypeScript setup' are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to 'this monorepo' with a clear niche (tsconfig base/leaf layering) and distinct, specific triggers, giving minimal conflict risk with other skills.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

EpicenterHQ/epicenter

Path

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