CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

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

82%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 strong, highly actionable reference skill: exact commands, complete boilerplate, and efficient tables with essentially no padding. The gaps are minor — a missing post-scaffold verification step, slightly winding Dev Scripts prose, and inline boilerplate that could be split out.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific facts in efficient tables and code blocks, with no explanations of concepts Claude already knows. It falls short of anchor 5 because the Dev Scripts prose section is winding and a few explanatory asides (e.g., the "This runs bun run --filter..." sentence) could be trimmed.

4 / 5

Actionability

Every section gives exact, executable material: a full command table, concrete script-name conventions, and copy-paste-ready package.json and tsconfig.json boilerplate covering the common new-package case. It matches the anchor for fully executable, copy-paste-ready guidance.

5 / 5

Workflow Clarity

Sequences are clear and the code-change workflow has an explicit validation checkpoint ("Run type checking to verify" via bun typecheck). It is not anchor 5 because the new-package workflow ends at "run bun install" without a verification step confirming the package registered and typechecks.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, and detail is appropriately deferred one level deep to well-signaled external pointers (the tsconfig skill for leaf tiers, docs/licensing/licensing-strategy.md). It falls short of anchor 5 because the full boilerplate listings are kept inline in a ~115-line body where a leaner overview with reference files could improve navigation.

4 / 5

Total

17

/

20

Passed

Description

70%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 compact description with an explicit, well-chosen trigger list that clearly outperforms the midpoint. Its main weakness is the what-clause, which lists topic nouns rather than concrete actions, limiting specificity and completeness.

DimensionReasoningScore

Specificity

"Monorepo scripts, package boilerplate, conventions" names the domain and its content areas but is a bare noun list rather than a set of concrete actions, matching the anchor for domain plus limited actions. It falls short of anchor 4 because no specific capabilities (e.g., "run scripts", "scaffold packages") are enumerated.

3 / 5

Completeness

Both what ("Monorepo scripts, package boilerplate, conventions") and when (explicit "Use when:" with concrete quoted triggers) are present, and the when is more specific than the anchor-4 example. It falls short of anchor 5 because the what is a terse topic list with no verbs, leaving "what does this skill do" only implicitly answered.

4 / 5

Trigger Term Quality

The Use-when clause lists natural phrases users would actually say ("how do I run", "run tests", "typecheck", "create a new package", "scaffolding packages"), giving good keyword coverage. It is not anchor 5 because common variations and synonyms (e.g., "new library", "format", "benchmark", "add a package") are missing.

4 / 5

Distinctiveness Conflict Risk

The monorepo framing plus bun-specific triggers ("bun run") establish a mostly distinct niche. Generic terms like "run tests", "linting", and "typecheck" create minor overlap risk with closely related build/test skills, keeping it below anchor 5.

4 / 5

Total

15

/

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/monorepo/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.