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

81%

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

75%Weight 40%Scale 1-5

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

Highly actionable, copy-paste-ready Nx exploration commands with good section structure and a properly signaled one-level reference. The chief weakness is redundancy — the Programmatic Answers section repeats earlier commands and includes bulky example JSON output.

Suggestions

Remove the 'Programmatic Answers' section or fold its unique bits (e.g. `jq 'length'`, `select(startswith(...))`) into the existing Listing/Project Details sections to eliminate duplication.

Trim or relocate the large illustrative JSON example outputs, keeping only the jq filters that operate on them.

Add a one-line validation hint in Troubleshooting (e.g. confirm `nx show project --json` succeeds before piping to `jq`) to strengthen the feedback loop for the failure cases.

Dimension	Reasoning	Score
Conciseness	The body is a mostly-efficient command reference, but the 'Programmatic Answers' section duplicates commands already shown in 'Listing Projects', 'Project Configuration', and 'Target Information', and large illustrative JSON output blocks pad the token budget.	3 / 5
Actionability	Copy-paste-ready `nx show`/`nx graph` commands with concrete `jq` filters cover the common exploration cases (listing, filtering, project config, targets, dependencies, troubleshooting) fully.	5 / 5
Workflow Clarity	The 'Common Exploration Patterns' section maps natural questions to concrete commands and Troubleshooting gives a sync→reset fallback, giving a clear sequence with minor gaps; no explicit validation checkpoints are needed for this read-only skill.	4 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled, one-level-deep reference to references/AFFECTED.md (a real bundle file), though the inlined Programmatic Answers section with large JSON blocks could be better separated.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 with an explicit 'USE WHEN' clause, multiple concrete trigger examples, and a clearly scoped Nx-workspace niche. The main weakness is slightly generic lead verbs ('explore', 'understand') in the 'what' statement.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Explore and understand Nx workspaces', 'check available targets/configuration before running a task', 'debug nx task failure' — but the lead verbs ('explore', 'understand') are somewhat generic, leaving minor gaps versus a fully concrete action list.	4 / 5
Completeness	Explicitly answers both what ('Explore and understand Nx workspaces', check targets/configuration, debug failures) and when via 'USE WHEN' / 'ALSO USE WHEN' clauses plus concrete EXAMPLES trigger phrases, matching the anchor for clearly answering both.	5 / 5
Trigger Term Quality	Natural user phrases like 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', and 'Cannot find configuration for task' give strong keyword coverage, though some common variations (e.g. 'affected projects', 'nx graph', 'build/lint') are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Nx workspaces) with distinct, nx-specific triggers ('nx command fails', 'configuration for task') that minimize overlap with other skills.	5 / 5
	Total	18 / 20 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: ae95bee

Reviewed: 1 day 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.