nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
85
66%
Does it follow best practices?
Impact
98%
1.25xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/developer-essentials/skills/nx-workspace-patterns/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Nx monorepos), provides an explicit 'Use when' clause with relevant trigger scenarios, and uses domain-specific terminology that minimizes conflict risk. The main weakness is that the core capability statement ('Configure and optimize') is somewhat broad, and the description could benefit from listing a few more concrete actions like generating projects, managing task pipelines, or configuring module federation.
Suggestions
Expand the leading capability statement with more concrete actions, e.g., 'Configure Nx monorepo workspaces, set up task pipelines, manage project graphs, and optimize build caching.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Nx monorepo workspaces) and some actions (configure, optimize, setting up, configuring project boundaries, optimizing build caching, implementing affected commands), but the leading phrase 'Configure and optimize' is somewhat generic. The trigger clause adds more specific actions, pushing it toward a 2-3 boundary, but the core description lacks a comprehensive list of concrete actions. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure and optimize Nx monorepo workspaces) and 'when' with an explicit 'Use when...' clause listing four specific trigger scenarios: setting up Nx, configuring project boundaries, optimizing build caching, and implementing affected commands. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Nx', 'monorepo', 'project boundaries', 'build caching', 'affected commands'. These are terms developers naturally use when working with Nx workspaces, covering the most common use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Nx monorepo is a very specific niche tool. The triggers like 'project boundaries', 'build caching', and 'affected commands' are distinctly Nx concepts, making it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, production-ready configuration templates and commands for Nx workspaces, which is its primary strength. However, it suffers from being a monolithic dump of large JSON/YAML/TypeScript templates that should be split into referenced files, and it lacks a clear sequential workflow with validation steps for setting up or configuring an Nx workspace. The content is far too verbose for inline consumption, competing heavily with conversation context.
Suggestions
Extract the large configuration templates (nx.json, project.json, eslintrc.json, custom generator, CI config) into separate referenced files and keep only a concise overview with links in SKILL.md
Add a clear step-by-step workflow for workspace setup with validation checkpoints (e.g., 'run nx graph to verify boundaries after configuring module boundary rules')
Remove the 'Core Concepts' architecture overview and library types table - these are well-documented Nx concepts Claude already knows; replace with only the actionable tagging conventions
Trim the project.json template to show only the essential/non-obvious configuration options rather than a complete file with standard boilerplate
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It includes extensive JSON configuration templates that could be referenced externally, explains concepts Claude already knows (library types table, architecture overview), and the 'Core Concepts' section adds little actionable value. The full project.json template with every configuration option is excessive inline content. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready configurations, commands, and code. The nx.json, project.json, ESLint config, custom generator TypeScript, CI YAML, and CLI commands are all concrete and complete. | 3 / 3 |
Workflow Clarity | While templates are well-organized, there's no clear sequenced workflow for setting up an Nx workspace from scratch. The 'Common Commands' section lists commands without sequencing. There are no validation checkpoints (e.g., verify the graph is correct after setting boundaries, validate config before committing). Migration steps are listed but lack error recovery guidance. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of configuration templates with no references to external files. The full nx.json, project.json, eslintrc.json, custom generator, CI config, and remote caching setup are all inline. These templates should be split into separate reference files with the SKILL.md providing an overview and links. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
70444e5
- Reviewed
Table of Contents
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.