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

76%

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

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

A highly actionable, code-rich skill body that gives Claude everything needed to execute, but it is padded with explanatory content Claude already knows, lacks validation checkpoints in its workflows, and references bundle files that are not present.

Suggestions

Remove or relocate the 'Why Monorepos?' advantages/challenges and Best Practices/Pitfalls sections, and drop the duplicate turbo.json under Build Optimization, to tighten conciseness.

Add explicit validation/verification steps to the publishing and CI workflows (e.g., 'verify packages build and lint before changeset publish') to add feedback loops.

Either create the referenced references/*.md, assets/*.md, and scripts/dependency-graph.ts files, or remove the dead Resources links, and move the bulky nx.json and CI YAML into those reference files.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable configs/commands, but the 'Why Monorepos?' advantages/challenges list, a redundant second turbo.json block under Build Optimization, and the Best Practices/Pitfalls sections restate concepts Claude already knows and could be trimmed.	3 / 5
Actionability	Abundant copy-paste-ready configs (turbo.json, nx.json, tsconfig, eslint) and concrete commands (pnpm --filter, nx affected, changesets) covering the common cases end to end.	5 / 5
Workflow Clarity	Setup and publishing sequences are present, but there are no validation checkpoints or feedback loops — e.g., changeset publish and CI runs proceed without verify steps, leaving sequence gaps that keep it at the 3-anchor.	3 / 5
Progressive Disclosure	Content is sectioned and a Resources section signals references, but large config blocks are inlined that belong in separate files, and the referenced references/assets/scripts files do not actually exist in the bundle, making the navigation partly dead.	3 / 5
	Total	14 / 20 Passed

Description

87%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 well-crafted description that explicitly states both capabilities and trigger conditions with concrete tooling terms. It is comprehensive and distinguishable, with only minor room for more synonym/extension coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'build efficient, scalable multi-package repositories with optimized builds and dependency management' — with only minor abstraction, so it sits above the 1-2-action anchor but below the fully comprehensive one.	4 / 5
Completeness	Clearly answers what ('Master monorepo management... to build efficient, scalable multi-package repositories') and when ('Use when setting up monorepos, optimizing builds, or managing shared dependencies') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('monorepos', 'Turborepo', 'Nx', 'pnpm workspaces', 'setting up monorepos', 'optimizing builds', 'shared dependencies'), missing only some synonyms/extension variants that the 5-anchor requires.	4 / 5
Distinctiveness Conflict Risk	A clear niche (monorepo management with named tools) with distinct triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 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: 6453c0b

Reviewed: about 9 hours 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.