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

88%

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

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.

An excellent conventions skill: lean, assumes Claude's competence, and gives copy-paste-ready configs plus an exact tier table. The only weak spots are the absence of an explicit typecheck-failure feedback loop and a single-file structure that, while well-organized, is longer than a minimal overview.

Dimension	Reasoning	Score
Conciseness	Dense and lean throughout — it assumes Claude knows TypeScript/tsconfig and never pads with basics; imperatives like 'Never use NodeNext', 'Delete on sight', and 'Do not add outDir' earn their tokens, and rationale is offloaded to the Background spec reference.	5 / 5
Actionability	Provides copy-paste-ready JSONC config blocks for both canonical library shapes, an exact tier table with precise 'extends' values and per-tier leaf options, and concrete commands ('bun install', 'bun typecheck') in the new-package steps.	5 / 5
Workflow Clarity	The 'Adding a new package' section is a clear 4-step sequence (scaffold → pick tier/copy shape → package.json setup → bun install + bun typecheck) with 'bun typecheck' as the verification checkpoint, but it lacks an explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	Well-organized into focused sections with a clearly signaled one-level-deep reference (Background → specs/...modernize-monorepo-tsconfig.md); no bundle files exist, and the ~128-line body is appropriately self-contained, though a conventions doc of this length could optionally split the canonical examples or never-redeclare list into a reference file.	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, concrete description that clearly states both what the skill covers and when to use it, with repo-specific triggers that distinguish it from generic TypeScript or scaffolding skills. The only minor gap is that the 'what' is framed as content nouns rather than performed actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete trigger-actions ('adding a package, editing any tsconfig.json, picking a tier for a new app, or debugging module resolution') and names specific content ('two-base layering, the seven leaf tiers, and the never-redeclare list'); the 'what' side leans on structural nouns rather than performed actions, so it sits at 4 rather than 5.	4 / 5
Completeness	Explicitly answers both 'what' (the conventions: two-base layering, seven leaf tiers, never-redeclare list) and 'when' with a concrete 'Use when...' clause enumerating four triggers.	5 / 5
Trigger Term Quality	Includes natural terms a user would actually say ('tsconfig.json', 'adding a package', 'picking a tier', 'module resolution'); good coverage but missing common synonyms like 'typecheck' or 'extends'.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to this monorepo's tsconfig conventions with distinctive triggers ('the two-base layering', 'the seven leaf tiers', 'debugging module resolution'), giving it a clear niche with minimal overlap risk.	5 / 5
	Total	18 / 20 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/tsconfig/SKILL.md
Commit: abe10f3

Reviewed: 5 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.