nx-workspace-patterns

Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.

1.19x

Quality

76%

Does it follow best practices?

Impact

99%

1.19x

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/nx-workspace-patterns/SKILL.md

The canonical home for this skill is nx-workspace-patterns 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, well-organized reference whose templates are executable and correct, but it is a monolithic single-file skill with no progressive disclosure and no sequenced workflows or validation checkpoints. The large inline config blocks also push against token efficiency since much of it restates standard Nx schema.

Suggestions

Move the bulky templates (nx.json, project.json, eslintrc boundaries, CI workflow) into references/ files (e.g. references/templates.md) and keep one condensed quick-start example inline, converting SKILL.md into an overview with clearly signaled one-level-deep references.

Add a short sequenced workflow with validation checkpoints, e.g. for boundary setup: add tags → add depConstraints → run `nx run-many -t lint` or `nx graph` to verify the graph is acyclic before proceeding.

Trim boilerplate config Claude already knows (full generator defaults, serve/test/lint target blocks) to reduce token cost without losing actionability, and flesh out or remove the "Migrating to Nx" use-case that has no corresponding steps.

Dimension	Reasoning	Score
Conciseness	The prose is lean (no concept tutorials), but ~300 lines of full configuration (complete nx.json, project.json, eslintrc) restate schema defaults and config Claude already knows or could derive. Mostly efficient yet could be significantly tightened by trimming boilerplate keys, so it sits at the 'could be tightened' anchor rather than clearly below (2) or above (4).	3 / 5
Actionability	All six templates are complete, executable, copy-paste ready: a full nx.json, project.json, eslint boundary rules, a working devkit generator, a GitHub Actions affected-workflow, and exact CLI commands with flags ("nx g @nx/react:lib feature-auth --directory=libs/web --tags=type:feature,scope:web"). Matches the fully-executable anchor with common cases covered.	5 / 5
Workflow Clarity	Content is organized by topic (architecture, templates, commands) but no multi-step process is sequenced with validation checkpoints — e.g., "Migrating to Nx" is listed in When to Use yet has no steps, and boundary enforcement never says to verify with lint/nx graph after adding tags. Sequence/checkpoints are implicit at best, matching the anchor-3 'validation gaps' description; not a 2 because the sections are coherent and the commands are correct.	3 / 5
Progressive Disclosure	Good section structure and clear headers, but the file is a ~450-line monolith with all six large templates inlined and zero reference files, so content that clearly belongs in separate files (full nx.json/project.json/CI templates) is inline. Not a 2 because structure is genuinely good and navigation within the file is easy; not a 4 because nothing is split out.	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 strong description: concise, third-person, with an explicit 'Use when' clause naming concrete Nx-specific triggers and capabilities. Its only weaknesses are modest keyword coverage (no mention of Nx Cloud, migrations, or dependency graphs) relative to what the skill body actually covers.

Suggestions

Add one or two high-frequency natural terms to the trigger clause, e.g. "setting up or migrating to Nx" and "Nx Cloud / remote caching", to broaden keyword coverage.

Consider mentioning generators or dependency-graph management in the what-clause, since these are first-class parts of the skill body.

Dimension	Reasoning	Score
Specificity	"Configure and optimize Nx monorepo workspaces" plus the when-clause actions ("setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands") list several concrete, specific actions. Not a 5 because coverage has minor gaps (e.g., generators, migrations, dependency management appear in the body but not the description).	4 / 5
Completeness	Clearly answers both: what ("Configure and optimize Nx monorepo workspaces") and when ("Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands") with multiple concrete trigger phrases. Matches the anchor-5 example structure; a 4 would require the 'when' to be less explicit than it is.	5 / 5
Trigger Term Quality	Natural terms users would say are present: "Nx", "monorepo", "workspaces", "project boundaries", "build caching", "affected commands". A few natural variations are missing ("Nx Cloud", "remote caching", "CI", "migrate", "dependency graph"), keeping it below comprehensive anchor 5; well above anchor 3's 'missing common variations'.	4 / 5
Distinctiveness Conflict Risk	"Nx monorepo workspaces" pins a clear niche with distinct, tool-specific triggers (Nx, affected commands, project boundaries); it would rarely fire for non-Nx skills. Minor theoretical overlap with generic caching/CI skills is not enough to drop to 4 since every trigger is Nx-anchored.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/nx-workspace-patterns/SKILL.md
Commit: 38d4f88

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.