Name: monorepo-management
Rating: 48 (1 reviews)
Author: administrakt0r

monorepo-management

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

Quality

51%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/monorepo-management/SKILL.md

The canonical home for this skill is monorepo-management in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

36%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 body is well-structured and lean but almost entirely generic, offering no concrete, executable guidance for monorepo work and relying on a referenced playbook file that is missing. It reads more like a template than a usable skill.

Suggestions

Replace the abstract Instructions with concrete, actionable guidance: name specific tools (e.g. npm/pnpm/yarn workspaces, Turborepo, Nx, Lerna), show example commands for workspace setup, dependency hoisting, and package versioning/publishing.

Add a real sequenced workflow with explicit validation checkpoints for at least the high-risk scenarios listed (e.g. multi-repo->monorepo migration, CI/CD setup) including a build/test verification step before proceeding.

Create the referenced 'resources/implementation-playbook.md' so the progressive-disclosure promise resolves, or remove the reference until the file exists.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows, but generic instruction bullets like 'Apply relevant best practices and validate outcomes' are filler that do not fully earn their place, keeping it just below a 5.	4 / 5
Actionability	The Instructions section is entirely abstract ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') with no concrete code, commands, tool names, or specific steps, matching the anchor for entirely vague guidance.	1 / 5
Workflow Clarity	A loose three-bullet pseudo-sequence exists (clarify -> apply -> provide steps), but the steps are meta-level directives rather than a real task workflow, with no explicit validation checkpoints despite monorepo migration/CI work being risky and non-simple.	2 / 5
Progressive Disclosure	In-body structure is clean with clearly signaled one-level references to 'resources/implementation-playbook.md', but that referenced file does not exist in the bundle, so the promised detailed patterns are not actually navigable, pulling it down from a 4.	3 / 5
	Total	10 / 20 Passed

Description

66%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 is concise, third-person, and names a distinct domain with several concrete capabilities, but it omits any explicit 'Use when' trigger guidance, capping completeness at 3. Adding a trigger clause with natural synonyms would lift the two lowest-weighted dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when setting up or migrating to a monorepo, managing shared dependencies across packages, or optimizing multi-package build and CI/CD performance.'

Include natural synonyms users might say, such as 'multi-package repo', 'polyrepo migration', or 'workspace setup', to broaden trigger-term coverage.

Reframe the capability list as distinct actions (e.g. 'Set up, migrate, and optimize monorepos for code sharing...') to read as multiple concrete actions rather than one action with benefits.

Dimension	Reasoning	Score
Specificity	Names the monorepo domain plus several concrete capabilities ('code sharing, consistent tooling, and atomic changes across multiple packages and applications'), but frames them as enablers of one action rather than a comprehensive list of distinct actions, so it falls short of a 5.	4 / 5
Completeness	The description gives a clear 'what' ('Build efficient, scalable monorepos...') but contains no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'monorepos' is a strong natural keyword a user would actually say, supported by related terms like 'code sharing' and 'packages and applications'; common synonyms such as 'multi-package repo' or 'polyrepo' are missing, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	'monorepo' carves out a fairly clear niche with low conflict risk, but without explicit trigger phrases it could still overlap with general project-setup or build/devops skills, so it is not a 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/monorepo-management/SKILL.md
Commit: 57c135b

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.