nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
52
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 monorepo workspaces), provides an explicit 'Use when' clause with relevant trigger scenarios, and uses domain-specific terminology that makes it highly distinguishable. The main weakness is that the primary capability statement ('Configure and optimize') is somewhat generic, and could benefit from listing more concrete actions like generating workspace configurations or setting up task pipelines.
| 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 primary verbs 'configure and optimize' are somewhat generic. The trigger clause adds more specific actions, pushing it toward a 2. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure and optimize Nx monorepo workspaces) and 'when' (explicit 'Use when' clause covering setting up Nx, configuring project boundaries, optimizing build caching, or 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. | 3 / 3 |
Distinctiveness Conflict Risk | Nx monorepo is a very specific niche tool. The triggers like 'Nx', 'project boundaries', 'affected commands', and 'build caching' are highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%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 conceptual overview of Nx monorepo patterns with no actionable, executable content. It describes library types and folder structures but provides zero CLI commands, configuration snippets, or step-by-step workflows. The deferral of all concrete templates to a non-existent bundle file leaves the skill hollow and unusable in practice.
Suggestions
Add concrete, executable examples: include actual nx.json configuration snippets, CLI commands like `npx nx affected:test --base=main`, and project.json boundary rules with enforce-module-boundaries lint config.
Define step-by-step workflows for key use cases (e.g., setting up a new workspace, configuring project boundaries, enabling remote caching) with explicit validation steps such as running `nx lint` to verify boundary rules.
Either include the referenced `references/details.md` as a bundle file or inline the most critical templates directly in the SKILL.md so the skill is self-contained enough to be useful.
Remove generic advice in the Do's/Don'ts section and replace with specific, Nx-configuration-level guidance (e.g., actual tag enforcement config, actual caching configuration in nx.json).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The library types table and architecture overview provide useful structure but include some content Claude would already know (e.g., what feature libs vs ui libs are). The 'When to Use This Skill' section is somewhat redundant with the description. The Do's/Don'ts are generic advice rather than Nx-specific actionable knowledge. | 2 / 3 |
Actionability | There are no executable commands, no concrete code examples, no nx.json configuration snippets, no CLI commands (e.g., `nx affected:test`, `nx generate`), and no copy-paste ready content. The skill describes concepts and categories but never instructs Claude on how to actually do anything. All concrete templates are deferred to a referenced file that doesn't exist in the bundle. | 1 / 3 |
Workflow Clarity | There are no sequenced steps for any workflow—setting up Nx, configuring boundaries, enabling caching, or running affected commands are all mentioned as use cases but none have a defined process. No validation checkpoints exist for any operation. | 1 / 3 |
Progressive Disclosure | The skill references `references/details.md` for templates and worked examples, which is a reasonable one-level-deep reference. However, no bundle files are provided, meaning the referenced file doesn't actually exist, and the main SKILL.md itself lacks enough substance to serve as a useful overview—it's mostly conceptual with all actionable content deferred. | 2 / 3 |
Total | 6 / 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
cf6059d
- 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.