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'.

1.40x

Quality

86%

Does it follow best practices?

Impact

90%

1.40x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

72%

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

A highly actionable, command-dense skill body with real example outputs and good progressive disclosure via a verified single reference file. It is held back by redundancy between the programmatic and earlier sections and by the absence of explicit validation/feedback checkpoints in its workflows.

Suggestions

Consolidate the duplicate listing/filtering/target-key commands between "Listing Projects"/"Target Information" and "Programmatic Answers" to remove redundancy and respect the token budget.

Add explicit validation/retry checkpoints to troubleshooting and exploration workflows (e.g., verify a target exists before running it, re-run `nx sync`/`nx reset` and confirm the error clears).

Trim assumed-knowledge sentences like "Targets define what tasks can be run on a project" that restate concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and command-focused, but there is redundancy: the "Programmatic Answers" section repeats listing/filtering/target-key commands already shown in "Listing Projects" and "Target Information", and explanatory headings like "Targets define what tasks can be run on a project" state what Claude already knows.	2 / 3
Actionability	Fully executable, copy-paste-ready commands with jq pipelines and realistic --json example outputs; explicit guidance such as "Do NOT read project.json directly" is concrete and actionable.	3 / 3
Workflow Clarity	The "Common Exploration Patterns" map questions to command sequences, but there are no validation/verification checkpoints and no explicit feedback loops; while mostly read-only, the troubleshooting flow lacks a clear validate-then-retry sequence.	2 / 3
Progressive Disclosure	The body is an overview with one clearly signaled one-level-deep reference ([references/AFFECTED.md]) that exists as a real file; content is split into well-organized sections with easy navigation.	3 / 3
	Total	10 / 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, well-structured description that names concrete capabilities and supplies explicit natural-language triggers plus example queries. It is concise without padding and clearly scoped to Nx workspace exploration.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: "Explore and understand Nx workspaces" plus checking "available targets/configuration before running a task" and "debug nx task failure".	3 / 3
Completeness	Clearly answers both what ("Explore and understand Nx workspaces") and when with explicit USE WHEN/ALSO USE WHEN triggers and concrete examples.	3 / 3
Trigger Term Quality	Good coverage of natural phrases users would say, e.g. "What projects are in this workspace?", "How is project X configured?", "What depends on library Y?", "Cannot find configuration for task", and "debug nx task failure".	3 / 3
Distinctiveness Conflict Risk	Narrowed to Nx workspace exploration with distinct triggers tied to nx commands and failures, making it unlikely to fire for unrelated skills.	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: leboncoin/spark-web
Path: .cursor/skills/nx-workspace/SKILL.md
Commit: 9f4792e

Reviewed: 5 days 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.