nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill nx-workspace-patterns83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
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.
This is a well-crafted skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes a clear 'Use when...' clause with natural trigger terms, and targets a distinct niche (Nx monorepos) that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'setting up Nx', 'configuring project boundaries', 'optimizing build caching', 'implementing affected commands'. These are distinct, actionable capabilities. | 3 / 3 |
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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 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 | Highly distinctive with Nx-specific terminology ('Nx monorepo', 'affected commands', 'project boundaries'). Unlikely to conflict with general build tools or other monorepo solutions like Turborepo or Lerna. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable templates and configurations for Nx workspaces with production-ready code examples. However, it lacks clear step-by-step workflows with validation checkpoints for complex operations like migrations, and the large inline templates make it verbose. The content would benefit from better progressive disclosure by moving detailed configurations to separate files.
Suggestions
Add explicit step-by-step workflows with validation checkpoints for key operations like 'Setting up a new workspace' and 'Migrating to Nx' - include verification steps after each major action
Move detailed template configurations (nx.json, project.json, eslintrc) to separate reference files and keep only minimal examples inline
Remove the library types table and core concepts section - Claude understands these patterns; focus on the specific configurations and commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory content like the 'Core Concepts' section explaining library types that Claude likely knows. The templates are comprehensive but could be trimmed - some configuration options are verbose. | 2 / 3 |
Actionability | Provides fully executable JSON configurations, TypeScript code for custom generators, complete YAML CI workflows, and copy-paste ready bash commands. All templates are production-ready and specific. | 3 / 3 |
Workflow Clarity | While commands and templates are clear, there's no explicit workflow sequence for common tasks like 'setting up a new workspace' or 'migrating to Nx'. The migration commands are listed but lack validation checkpoints or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document with 6 large templates inline. The external resources at the end are good, but detailed configurations could be split into separate reference files. | 2 / 3 |
Total | 9 / 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.
- 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.