CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

monorepo-management

Build efficient, scalable monorepos that enable code sharing, consistent tooling, and atomic changes across multiple packages and applications.

48

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/monorepo-management/SKILL.md

The canonical home for this skill is monorepo-management in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The skill has a clean, token-efficient skeleton with a well-signaled reference structure, but delivers almost no monorepo-specific substance: the instructions are boilerplate, no executable workflow exists, and the referenced playbook file is missing from the bundle entirely.

Suggestions

Replace the generic Instructions ('Clarify goals... Apply relevant best practices') with monorepo-specific guidance, e.g. concrete tool choices (pnpm workspaces, Nx, Turborepo) and a minimal workspace-config example.

Add the referenced resources/implementation-playbook.md to the bundle, or remove the reference — as written, Claude will try to open a file that does not exist.

Sequence the core workflows (e.g. migration, package versioning/publishing) into numbered steps with explicit validation checkpoints, since these are multi-step and error-prone operations.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) and assumes Claude's competence with no explanation of known concepts. Minor filler such as 'The task is unrelated to monorepo management' and generic instruction bullets keep it below a 5.

4 / 5

Actionability

The instructions are entirely generic ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.') with no monorepo-specific guidance, commands, tool names, or config examples. The use-case bullets are concrete scenarios but not executable steps, and the promised playbook does not exist in the bundle.

2 / 5

Workflow Clarity

There is no sequenced workflow for inherently multi-step work like migration, CI/CD setup, or publishing; validation appears only abstractly as 'validate outcomes' and 'verification'. A loose meta-order (clarify, apply, verify) keeps it above a 1, but no actual executable step sequence exists.

2 / 5

Progressive Disclosure

Sections are well organized and the single reference to 'resources/implementation-playbook.md' is clearly signaled and one level deep, but that file does not exist in the bundle (no resources/, references/, scripts/, or assets/ directories), so the disclosure chain is broken in practice.

3 / 5

Total

11

/

20

Passed

Description

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

The description clearly communicates what the skill does and occupies a distinct niche, but it completely lacks 'when to use' trigger guidance and leans on a single keyword. Adding an explicit use-when clause with common synonyms would lift the two weakest dimensions.

Suggestions

Append a trigger clause, e.g. 'Use when setting up, migrating to, or scaling a monorepo, or when the user mentions monorepos, multi-package repos, or workspaces.'

Include natural synonyms users actually say — multi-package repo, polyrepo migration, pnpm workspaces, Nx, Turborepo — to broaden trigger-term coverage.

Optionally enumerate one or two more concrete actions (migrate from multi-repo, version and publish shared packages) to round out capability coverage.

DimensionReasoningScore

Specificity

It names the domain and several concrete capabilities — 'enable code sharing, consistent tooling, and atomic changes across multiple packages and applications'. Not a 5 because it states properties rather than a comprehensive list of concrete actions (no migrating, versioning, or publishing).

4 / 5

Completeness

It has a clear 'what' ('Build efficient, scalable monorepos...') but no 'Use when...' clause or equivalent trigger guidance at all, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'monorepos' is the only natural keyword users would say. Missing common variations and synonyms such as multi-package repo, workspaces, pnpm workspaces, Nx, or Turborepo, so coverage is not good enough for a 4.

3 / 5

Distinctiveness Conflict Risk

'monorepo' is a clear, distinct niche term unlikely to fire for unrelated skills. Minor overlap risk remains with closely related versioning, publishing, or CI-setup skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/monorepo-management/SKILL.md

Revision

64adc55

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill