CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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 tight, highly actionable monorepo skill with concrete commands and complete boilerplate templates, plus an explicit verification step. The only real weakness is verbose inline rationale in the declaration build gate section that could be trimmed or split out.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence with no basic-concept padding; the multi-paragraph declaration build gate rationale is valuable but somewhat long and could be tightened.

4 / 5

Actionability

Concrete commands throughout and complete, copy-paste-ready package.json and tsconfig.json boilerplate covering the common new-package and verification cases.

5 / 5

Workflow Clarity

Sequenced new-package flow and an explicit 'After Completing Code Changes' typecheck verification step; minor gaps such as no explicit validation after scaffolding a package.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references (the tsconfig skill, docs/licensing/licensing-strategy.md) and no nested references; some long inline rationale could live in a separate file.

4 / 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, trigger-rich description that explicitly pairs a what-statement with a concrete 'Use when' clause using natural user phrasing. The main weakness is the noun-based capability summary and the lack of synonyms/file extensions in the trigger list.

DimensionReasoningScore

Specificity

The 'what' is a noun list ('Monorepo scripts, package boilerplate, conventions') but the Use-when clause names many concrete actions (run, build, test, typecheck, lint, scaffold); not a 5 because the capability statement itself is not verb-driven.

4 / 5

Completeness

Explicitly states what the skill covers and follows with a concrete 'Use when:' clause listing specific trigger phrases, matching the anchor for both what and when.

5 / 5

Trigger Term Quality

Quoted natural user phrases like 'how do I run', 'build this', 'run tests', 'typecheck' are exactly what a user would say; held at 4 because synonyms and file extensions are mostly absent.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche around this bun-based monorepo's dev workflows with distinct triggers, but overlaps slightly with referenced sibling skills (tsconfig, licensing).

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EpicenterHQ/epicenter
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.