Name: monorepo-management
Rating: 33.6 (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

29%

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/skills/monorepo-management/SKILL.md

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

Quality

Content

22%Scale 1-5

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

This skill is essentially a placeholder with no actionable content. It lists when to use the skill and defers everything to a referenced playbook that doesn't exist in the bundle. The instructions are entirely generic boilerplate that could apply to any skill and provide zero monorepo-specific guidance.

Suggestions

Add concrete, executable examples for at least one monorepo tool (e.g., Nx, Turborepo, or pnpm workspaces) with actual configuration files and commands.

Replace the generic instruction bullets with specific workflow steps, such as 'Initialize workspace with `npx create-turbo@latest`' or provide a workspace configuration example.

Include validation/verification steps such as checking dependency graphs, running affected tests, or verifying package resolution.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns and examples directly in the SKILL.md.

Dimension	Reasoning	Score
Conciseness	The skill is relatively short, but the 'Use this skill when' and 'Do not use this skill when' sections are padded with generic items that don't add value. The instructions section is vague boilerplate ('Clarify goals, constraints, and required inputs') rather than domain-specific content.	3 / 5
Actionability	The skill provides no concrete code, commands, configuration examples, or specific steps. Every instruction is abstract and vague ('Apply relevant best practices and validate outcomes'). There is nothing executable or copy-paste ready.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The four bullet points in Instructions are generic platitudes with no sequencing, no validation checkpoints, and no specific steps for any monorepo operation.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files are provided, so we cannot verify the reference exists or contains useful content. The SKILL.md itself is too thin to serve as a useful overview.	3 / 5
	Total	8 / 20 Passed

Description

36%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 identifies the monorepo domain but relies on abstract benefits (code sharing, consistent tooling, atomic changes) rather than concrete actions. It lacks a 'Use when...' clause, specific tool names, and actionable trigger terms that would help Claude distinguish this skill from general project setup or package management skills.

Suggestions

Add a 'Use when...' clause with trigger terms like 'monorepo', 'workspace setup', 'multi-package project', 'Nx', 'Turborepo', 'Lerna', or 'yarn/pnpm workspaces'.

Replace abstract benefits with concrete actions such as 'Configure workspace dependencies, set up shared build pipelines, manage inter-package imports, and configure task orchestration with tools like Nx or Turborepo'.

Include file extensions or config file names users might mention, such as 'nx.json', 'turbo.json', 'pnpm-workspace.yaml', or 'lerna.json' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (monorepos) but the actions listed ('code sharing, consistent tooling, atomic changes') are high-level concepts rather than concrete actions. It doesn't specify what tools, commands, or configurations are involved.	2 / 5
Completeness	Has a vague 'what' (build monorepos with code sharing, tooling, atomic changes) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which per the rubric caps this at 3, and the 'what' is also not very concrete, bringing it to 2.	2 / 5
Trigger Term Quality	Includes 'monorepos' and 'packages' which are relevant keywords, but misses natural terms users would say like 'Nx', 'Turborepo', 'Lerna', 'workspace', 'pnpm workspaces', 'yarn workspaces', or specific tool names that would trigger selection.	3 / 5
Distinctiveness Conflict Risk	The term 'monorepos' provides some specificity, but 'code sharing' and 'consistent tooling' are broad enough to overlap with general project setup, CI/CD, or package management skills. The description doesn't clearly carve out a distinct niche.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/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.