monorepo

Monorepo scripts, package boilerplate, conventions. Use when: "how do I run", "bun run", "build this", "run tests", "typecheck", "create a new package", linting, scaffolding packages.

Quality

96%

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

100%

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

A dense, well-organized reference that earns its tokens with executable commands, complete boilerplate, explicit verification checkpoints, and clean deferral of deeper detail to external files. No bundle files are present, but the body appropriately points to real external references.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence throughout — tables and terse convention notes convey high information density without explaining concepts Claude already knows.	3 / 3
Actionability	Provides fully executable commands and complete, copy-paste-ready package.json/tsconfig.json examples plus concrete CLI invocations.	3 / 3
Workflow Clarity	The 'After Completing Code Changes' section gives an explicit verify checkpoint (bun typecheck), and package creation ends with a registration step (bun install), sequencing the workflow with validation.	3 / 3
Progressive Disclosure	Keeps the overview inline while clearly signaling one-level-deep detail in external files — 'lives in packages/cli/README.md', 'See docs/licensing/licensing-strategy.md', 'see the tsconfig skill' — with no nested chains.	3 / 3
	Total	12 / 12 Passed

Description

92%

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 well-crafted description that clearly states its domain and pairs it with natural, varied trigger terms via an explicit 'Use when' clause. Its only weakness is mild overlap risk with generic build/test/lint skills.

Suggestions

Tighten trigger terms that overlap with general CI/build skills (e.g. 'run tests', 'linting') by qualifying them with the monorepo context to improve distinctiveness.

Consider a single distinguishing phrase that anchors the skill specifically to monorepo workspace/package concerns versus ordinary repo tasks.

Dimension	Reasoning	Score
Specificity	Names multiple concrete domains — 'Monorepo scripts, package boilerplate, conventions' — listing specific capabilities rather than vague actions.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via the 'Use when:' clause with concrete triggers.	3 / 3
Trigger Term Quality	Includes natural phrases users actually say — 'how do I run', 'bun run', 'build this', 'run tests', 'typecheck', 'create a new package', 'linting', 'scaffolding' — with broad coverage.	3 / 3
Distinctiveness Conflict Risk	The monorepo scope gives it a niche, but generic terms like 'linting', 'run tests', and 'build this' could overlap with a general CI or test/build skill.	2 / 3
	Total	11 / 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/monorepo/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.