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

—

Does it follow best practices?

Impact

99%

1.19x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, lean-prose reference of executable Nx config templates and commands, weakened only by inline-heavy organization and missing validation checkpoints for migration/reset operations.

Suggestions

Add explicit validation/feedback steps around risky flows — e.g., run `nx migrate latest`, review `migrations.json`, then `nx migrate --run-migrations`, and re-run `nx affected -t lint test` to confirm; warn that `nx reset` clears the cache.

Move the largest config blocks (full nx.json, project.json, .eslintrc.json, and the generator) into files under references/ and link to them one level deep, keeping SKILL.md as an overview.

Add a short sequenced "Setup workflow" (init → tag libs → set boundaries → enable caching → wire affected CI) so the multi-step path is explicit rather than implied by scattered templates.

Dimension	Reasoning	Score
Conciseness	Prose is lean with no explanation of concepts Claude already knows (no "Nx is a monorepo tool..." preamble); nearly every token is actionable config or commands, though the total volume is large.	3 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts (nx.json, project.json, .eslintrc.json, a TypeScript generator, CI yaml, and concrete nx commands) rather than vague or pseudocode guidance.	3 / 3
Workflow Clarity	The CI section is sequenced, but risky/batch flows like `nx migrate latest` / `nx migrate --run-migrations` and the destructive `nx reset` lack validation checkpoints or warnings, capping clarity at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Content is well-sectioned but, at ~450 lines with no references/scripts/assets bundle, large templates that could live in separate reference files are all inline; the under-50-line exception does not apply.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, well-constructed description that states concrete capabilities and gives explicit "Use when" triggers with natural keywords, answering both what and when without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands" — matching the multi-action anchor rather than the single-domain score-2 example.	3 / 3
Completeness	An explicit "Use when..." clause answers both what ("Configure and optimize Nx monorepo workspaces") and when with explicit triggers, satisfying the score-3 anchor; not the implied-when score-2 case.	3 / 3
Trigger Term Quality	Natural terms a user would say ("Nx monorepo workspaces", "project boundaries", "build caching", "affected commands") are well covered; not jargon-only or generic.	3 / 3
Distinctiveness Conflict Risk	The Nx-monorepo niche with Nx-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: e9f9b67

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