monorepo-architect

Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,

Quality

39%

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

Quality

Content

17%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 high-level outline with no actionable content. It lists capabilities and workflow steps at an abstract level without providing any concrete code, configuration examples, or tool-specific commands. The best practices are generic advice that Claude already knows, and the referenced playbook file doesn't exist in the bundle.

Suggestions

Add concrete, executable examples for at least the most common tools (e.g., `npx create-nx-workspace`, Turborepo `turbo.json` configuration, Bazel `BUILD` file snippets) to dramatically improve actionability.

Replace the generic best practices with tool-specific configuration patterns, gotchas, and decision criteria (e.g., 'Choose Nx when X, Turborepo when Y, Bazel when Z' with concrete thresholds).

Add validation checkpoints to the workflow, such as 'Verify dependency graph: `nx graph` should show no circular dependencies' or 'Test cache hit: run build twice, second should complete in <5s'.

Either create the referenced `resources/implementation-playbook.md` with detailed implementation guides, or inline the essential content directly in the skill.

Dimension	Reasoning	Score
Conciseness	The skill contains significant padding: a 'Capabilities' section listing things Claude already knows, a 'Use this skill when' section that largely restates the description, and 'Do not use this skill when' with tautological guidance. The best practices are generic platitudes rather than specific, actionable knowledge.	2 / 5
Actionability	There is no concrete, executable guidance anywhere—no code examples, no specific commands, no configuration snippets, no tool-specific syntax. Everything is abstract direction like 'Configure build caching strategy' and 'Select appropriate monorepo tooling' without showing how.	1 / 5
Workflow Clarity	The workflow lists 8 high-level steps but they are vaguely defined with no validation checkpoints, no feedback loops, and no concrete commands. Steps like 'Assess codebase size' and 'Design workspace and project structure' give no indication of what to actually do or how to verify success.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` but no bundle files exist, making this a broken reference. The SKILL.md itself is a flat list of generic sections with no meaningful structure or navigation to deeper content.	2 / 5
	Total	7 / 20 Passed

Description

61%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 a clear domain (monorepo architecture) and names specific tools, which aids in skill selection. However, it appears truncated, cutting off mid-sentence in the 'Use when' clause, which undermines completeness. The use of 'Masters' and 'Expert in' is fluffy self-description rather than concrete action statements.

Suggestions

Complete the truncated 'Use when' clause with specific trigger scenarios, e.g., 'Use when setting up monorepos, configuring workspace builds, managing cross-project dependencies, or working with Nx/Turborepo/Bazel/Lerna.'

Replace vague phrases like 'Expert in' and 'Masters' with concrete action verbs describing what the skill does, e.g., 'Configures monorepo workspaces, sets up build pipelines, manages cross-package dependencies, and optimizes build caching.'

Add common synonyms and related terms like 'workspace', 'multi-package repo', 'pnpm workspaces', 'yarn workspaces' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (monorepo architecture) and lists specific tools (Nx, Turborepo, Bazel, Lerna), but the actions described are vague ('efficient multi-project development') and the description appears truncated, cutting off at 'monorepo setup,'.	3 / 5
Completeness	The 'what' is partially covered (monorepo architecture, build systems, dependency management) and there's a truncated 'when' clause ('Use PROACTIVELY for monorepo setup,'). The description is cut off, so the 'when' guidance is incomplete, capping this at 3.	3 / 5
Trigger Term Quality	Includes strong trigger terms like 'monorepo', 'Nx', 'Turborepo', 'Bazel', 'Lerna', 'build systems', 'dependency management' that users would naturally use. Missing some variations like 'workspace', 'multi-package', 'pnpm workspaces', or 'yarn workspaces'.	4 / 5
Distinctiveness Conflict Risk	The focus on monorepo-specific tools (Nx, Turborepo, Bazel, Lerna) creates a fairly distinct niche. There's minor overlap risk with general build system or dependency management skills, but the monorepo framing is distinctive enough.	4 / 5
	Total	14 / 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: skills/monorepo-architect/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.