monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
81
66%
Does it follow best practices?
Impact
90%
1.12xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/developer-essentials/skills/monorepo-management/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly identifies its niche (monorepo management), names specific tools, and includes an explicit 'Use when' clause with relevant triggers. Its main weakness is that the capability descriptions lean slightly toward marketing language ('Master', 'efficient, scalable') rather than listing more granular concrete actions. The trigger terms are well-chosen and cover the natural vocabulary users would employ.
Suggestions
Replace the aspirational opener 'Master monorepo management' with more concrete actions like 'Configures task pipelines, sets up shared configs, manages workspace dependencies' to improve specificity.
Remove marketing-style adjectives like 'efficient, scalable' and replace with additional concrete capabilities such as 'configure caching strategies, define package boundaries, set up CI pipelines for monorepos.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (monorepo management) and some tools (Turborepo, Nx, pnpm workspaces), and mentions actions like 'optimized builds and dependency management,' but these are fairly high-level rather than listing multiple concrete discrete actions like 'configure task pipelines, set up shared configs, manage workspace dependencies.' | 2 / 3 |
Completeness | Clearly answers both 'what' (monorepo management with Turborepo, Nx, pnpm workspaces for multi-package repos with optimized builds and dependency management) and 'when' (explicit 'Use when setting up monorepos, optimizing builds, or managing shared dependencies'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'monorepo', 'Turborepo', 'Nx', 'pnpm workspaces', 'multi-package repositories', 'builds', 'shared dependencies'. These cover the main terms a user would naturally use when seeking help with monorepo tooling. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of monorepo-specific tools (Turborepo, Nx, pnpm workspaces) and the focus on multi-package repository management creates a clear niche that is unlikely to conflict with general build tools, package management, or other development skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent executable examples and real-world configurations, but it suffers severely from verbosity and poor organization. It tries to be a comprehensive reference for three different tools (Turborepo, Nx, pnpm) plus CI/CD, publishing, and code sharing patterns all in one file, resulting in a massive document that wastes context window. The content would benefit enormously from splitting into focused sub-files and removing explanatory content Claude already knows.
Suggestions
Remove the 'Core Concepts' section entirely (Why Monorepos advantages/challenges, tool comparisons) — Claude already knows these concepts and they consume tokens without adding actionable value.
Split into focused sub-files: keep SKILL.md as a brief overview with links to TURBOREPO.md, NX.md, PNPM.md, CI-CD.md, and PUBLISHING.md for detailed configs and examples.
Add explicit validation checkpoints to the setup workflow, e.g., 'After creating the workspace, run `pnpm install && pnpm turbo run build` to verify the dependency graph resolves correctly.'
Remove one of the build system sections (Turborepo OR Nx) from the main file since covering both in full detail is redundant — pick the recommended one and reference the other in a separate file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains basic concepts Claude already knows (why monorepos, advantages/challenges lists, what shared types are). The 'Core Concepts' section is entirely unnecessary padding. Multiple full config files and code patterns that could be referenced externally bloat the content significantly. | 1 / 3 |
Actionability | Provides fully executable code, commands, and configuration files throughout. Every section includes copy-paste ready examples: bash commands for setup, complete JSON configs for turbo.json/package.json, TypeScript component examples, CI/CD YAML workflows, and pnpm commands with specific flags. | 3 / 3 |
Workflow Clarity | While individual sections have clear commands, there's no cohesive multi-step workflow with validation checkpoints. Setting up a monorepo is inherently multi-step, but the skill presents disconnected sections rather than a sequenced process. No validation steps (e.g., verify workspace setup works, check dependency graph is acyclic) are included despite the complexity of the operations. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—Turborepo setup, Nx setup, pnpm workspaces, shared configs, CI/CD, publishing—is inlined in a single massive document. This should be split into separate files (e.g., TURBOREPO.md, NX.md, CI-CD.md) with the main skill providing an overview and navigation. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (615 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
27a7ed9
- 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.