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 keywords, explicit 'Use when' and 'Do NOT use' clauses, and clearly distinguishes itself from related skills. The negative boundary clauses referencing sibling skills are particularly effective for disambiguation 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 explicit negative boundaries ('Do NOT use for...') which further clarifies when to use it. | 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 clear niche (Nx monorepo workspace configuration/optimization) and explicitly delineates boundaries by naming two sibling skills (nx-run-tasks, nx-generate) and what they handle, minimizing conflict risk. | 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 skill with strong actionability and excellent progressive disclosure. The main weaknesses are minor conciseness issues (some content overlap and inclusion of information Claude already knows like library type conventions) and a lack of explicit validation steps in workflows. The critical insight about using `nx show project` instead of reading project.json directly is particularly valuable.
Suggestions
Remove the library types table and workspace architecture diagram — these are general Nx conventions Claude likely already knows, and they're better suited for the reference files.
Add a validation/verification step to multi-step workflows, e.g., after running affected commands, verify the project list before proceeding with batch operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundancy — the 'Run Tasks' section overlaps with Quick Start, the library types table and workspace architecture diagram add context Claude likely already knows, and the description says NOT to use this for running tasks yet running tasks is covered. Some tightening possible. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, with concrete examples like `nx show project my-app --json | jq '.targets | keys'`. The critical warning about not reading project.json directly is a high-value, non-obvious insight. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | The 'Common Workflows' section provides clear question-answer patterns, but there are no explicit validation checkpoints or feedback loops for multi-step operations. The workflows are more like individual commands than sequenced processes with verification steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to configuration, commands, CI/CD, and best practices files. Each reference clearly lists 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
81e7e0d
- 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.