nx-workspace

Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized command catalog for read-only Nx workspace exploration with no fragile multi-step operations. Its one weakness is repetition across sections that inflates the token budget without adding capability.

Suggestions

Consolidate the `--affected` examples into the single 'Affected Projects' section and reference it elsewhere instead of re-listing the same `--base`/`--type`/`--exclude` variants in 'Listing Projects' and 'Common Exploration Patterns'.

Merge the overlapping target-listing commands (`jq '.targets | keys'`, `--withTarget serve/e2e`) that currently appear in both 'Project Configuration' and 'Target Information' into one location.

Tighten the 'Targets define what tasks can be run on a project.' line — Nx 'targets' are domain-specific, but the definition is not needed given the immediately following executable examples.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and avoids explaining concepts Claude already knows, but it is not lean — the `--affected` examples recur across three sections, `--withTarget serve/e2e` across two, and `nx show project ... \| jq '.targets \| keys'` appears in both Project Configuration and Target Information, so not every token earns its place.	2 / 3
Actionability	Guidance is fully executable and copy-paste ready throughout — concrete `nx show projects`/`nx show project ... --json \| jq ...` commands plus fallbacks like `grep -r` and `git diff --name-only`, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	This is a read-only exploration skill with no destructive or batch operations requiring validation checkpoints, and the Common Exploration Patterns section maps each user question to specific commands; per the simple-skill scoring note, unambiguous single-action workflows may score 3.	3 / 3
Progressive Disclosure	No bundle files exist and the body is a well-organized single-file catalog with clearly headed sections and no nested references; the only file references point to external node_modules schemas, so the self-contained structure is appropriate.	3 / 3
	Total	11 / 12 Passed

Description

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.

A strong description that pairs a concise capability statement with an explicit USE WHEN trigger clause and natural-language example queries. It is specific, well-triggered, complete, and distinctively scoped to Nx workspaces.

Dimension	Reasoning	Score
Specificity	The lead phrase 'Explore and understand Nx workspaces' is mildly abstract, but the EXAMPLES enumerate multiple concrete operations — listing projects, inspecting configuration, finding targets, affected projects, and dependents — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers both 'what' ('Explore and understand Nx workspaces') and 'when' via the explicit 'USE WHEN answering any questions about the nx workspace...' clause with worked examples, using third-person voice throughout.	3 / 3
Trigger Term Quality	Natural user phrasings are quoted verbatim ('What projects are in this workspace?', 'What's affected by my changes?', 'Which projects depend on library Y?') alongside domain terms (nx workspace, projects, targets, tasks), giving strong coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	It targets a clear, specialized niche (Nx workspaces) with domain-specific triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nrwl/nx
Path: .agents/skills/nx-workspace/SKILL.md
Commit: 0abf7a4

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

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.