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.

1.34x

Quality

68%

Does it follow best practices?

Impact

93%

1.34x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/monorepo-management/SKILL.md

The canonical home for this skill is monorepo-management in wshobson/agents

Quality

Content

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

Highly actionable reference material undermined by verbosity and a broken bundle structure: the referenced files are missing and their content is inlined instead. It reads as a reference manual rather than a guided workflow, with no validation checkpoints for build/deploy operations.

Suggestions

Create the referenced bundle files and move the per-tool deep dives (full Turborepo/Nx/pnpm configurations, CI YAML, publishing flow) into them, keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

Cut content Claude already knows — the 'Why Monorepos?' pros/cons lists and the trivial Button/capitalize/truncate code examples — and trim or section off pinned version numbers (turbo ^1.10.0, pnpm@8, node 18).

Add validation checkpoints to the operational sequences, e.g. verify `pnpm turbo run build` succeeds before deploy and check `nx graph`/dependency output for cycles before publishing.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose across several sections: "Why Monorepos?" lists advantages/challenges Claude already knows, the code-sharing patterns include trivial Button/capitalize/truncate implementations, and pinned versions ("turbo ^1.10.0", "pnpm@8.0.0", "node-version: 18") are time-sensitive with no deprecated-section framing.	2 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: "npx create-turbo@latest my-monorepo", "pnpm add react --filter @repo/ui", complete turbo.json/nx.json/CI YAML files, and the changesets publish flow cover the common cases.	5 / 5
Workflow Clarity	Content is organized as topical reference sections rather than a sequenced workflow, and validation checkpoints are absent throughout — e.g. the deploy-affected step ("pnpm --filter web deploy") runs with no verification, and no section validates that a build/install succeeded.	3 / 5
Progressive Disclosure	All six referenced bundle files (references/turborepo-guide.md, references/nx-guide.md, references/pnpm-workspaces.md, assets/monorepo-checklist.md, assets/migration-guide.md, scripts/dependency-graph.ts) do not exist, while ~400 lines of per-tool configuration detail that belongs in those files is inlined in SKILL.md.	2 / 5
	Total	12 / 20 Passed

Description

82%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 description with an explicit 'Use when...' clause, clear tool-level distinctiveness, and good natural trigger terms. Its main weakness is buzzword padding ('Master', 'efficient, scalable', 'optimized') where more concrete capability statements could go.

Suggestions

Replace buzzwords like 'Master... efficient, scalable... optimized' with concrete capabilities, e.g. 'Configure Turborepo pipelines and caching, set up pnpm workspace filtering, and generate Nx apps and libraries'.

Add common user phrasings as triggers, e.g. 'multi-package repo', 'workspace', or 'shared packages between apps'.

Dimension	Reasoning	Score
Specificity	Names the domain and tools ("Turborepo, Nx, and pnpm workspaces") plus a few actions ("setting up monorepos, optimizing builds, or managing shared dependencies"), but "Master monorepo management... efficient, scalable... optimized builds" is generic, buzzword-tinged language rather than comprehensive concrete actions.	3 / 5
Completeness	Explicitly answers both what ("build... multi-package repositories with optimized builds and dependency management") and when ("Use when setting up monorepos, optimizing builds, or managing shared dependencies") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage — "monorepo", "Turborepo", "Nx", "pnpm workspaces", "builds", "dependencies" — but misses common variations like "multi-package repository" and bare "workspaces".	4 / 5
Distinctiveness Conflict Risk	Naming the specific tools (Turborepo, Nx, pnpm workspaces) carves a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (624 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	14 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/monorepo-management/SKILL.md
Commit: a65ce00

Reviewed: 6 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.