nx-workspace
Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT use for running tasks (use nx-run-tasks) or code generation with generators (use nx-generate).
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 an excellent skill description that covers all key dimensions thoroughly. It provides specific actions, natural trigger terms, explicit 'Use when' and 'Do NOT use' clauses, and clear disambiguation from related skills. The negative boundary guidance ('Do NOT use for...') is a particularly strong feature that minimizes conflict risk in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure, explore, and optimize Nx monorepo workspaces', 'setting up Nx', 'exploring workspace structure', 'configuring project boundaries', 'analyzing affected projects', 'optimizing build caching', 'implementing CI/CD with affected commands'. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure, explore, optimize Nx monorepo workspaces) and 'when' (explicit 'Use when...' clause listing six specific trigger scenarios). Also includes 'Do NOT use' guidance for disambiguation, which strengthens the 'when' component. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'nx', 'monorepo', 'workspace', 'projects', 'targets', 'affected', 'build caching', 'CI/CD', 'project boundaries'. These cover common variations of how users would describe Nx workspace tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting via 'Do NOT use for running tasks (use nx-run-tasks) or code generation with generators (use nx-generate)', which directly addresses potential conflicts with related Nx skills and creates a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured Nx workspace management skill with strong actionability and excellent progressive disclosure. The main weaknesses are minor verbosity (the library types table and architecture diagram may be unnecessary for Claude) and the lack of explicit validation steps in multi-step workflows. The critical warning about using `nx show project --json` instead of reading project.json directly is a valuable, non-obvious insight.
Suggestions
Remove or significantly trim the 'Workspace Architecture' section and 'Library Types' table — Claude already understands monorepo conventions and this information is better suited for the reference files.
Add a brief multi-step workflow with validation checkpoints (e.g., setting up module boundaries or configuring caching) to improve workflow clarity for more complex operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundancy — the 'Run Tasks' section overlaps with the Quick Start, and the library types table and workspace architecture diagram add context Claude likely already knows. The note about npx/pnpx/yarn is borderline unnecessary. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, including concrete examples with jq piping, specific flags, and real command patterns. The critical warning about `nx show project` vs reading `project.json` directly is highly actionable and non-obvious. | 3 / 3 |
Workflow Clarity | The 'Common Workflows' section provides clear question-to-command mappings, and the Quick Troubleshooting section is helpful. However, there are no explicit validation checkpoints or feedback loops for multi-step operations like workspace setup or CI configuration — these are deferred entirely to reference files. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and clearly signaled one-level-deep references to configuration, commands, CI/CD, and best practices files. Each reference includes a brief description of what it contains, making navigation easy. | 3 / 3 |
Total | 10 / 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
- tech-leads-club/agent-skills
- Commit
906a57d
- 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.