CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nx-workspace

Explore and understand Nx workspaces. USE WHEN answering any questions about the nx workspace, the projects in it or tasks to run. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What targets can I run?', 'What's affected by my changes?', 'Which projects depend on library Y?', or any questions about Nx workspace structure, project configuration, or available tasks.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/nx-workspace/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A highly actionable, code-first reference that assumes Claude's competence and gives real, executable nx CLI and jq commands organized by task. The main quality issues are redundancy — flags and jq examples repeated across three sections plus a duplicated (and mislabeled) schema-pointer sentence — and a couple of shallow 'common patterns' that don't fully answer the questions they head.

Suggestions

Deduplicate: keep the full flag catalog in 'Listing Projects' only, and have 'Affected Projects' and 'Common Exploration Patterns' reference it instead of repeating the same commands.

Fix the second schema-pointer sentence (line 98): it says 'project schema' but links node_modules/nx/schemas/nx-schema.json — correct it to 'workspace/nx schema' and keep just one copy.

Strengthen the 'Why is project X affected?' pattern with the actual mechanism (e.g., nx graph --file or checking project dependencies) rather than only git diff plus the project root.

DimensionReasoningScore

Conciseness

The command-per-line style is efficient and assumes Claude's competence (no Nx tutorials or concept explanations), but there is noticeable duplication: the affected/filter flags appear in both 'Listing Projects' and 'Affected Projects', the jq target examples appear in both 'Project Configuration' and 'Target Information', the 'Common Exploration Patterns' repeat commands a third time, and the schema-pointer sentence appears twice (line 52 and line 98) — the second copy is even mislabeled, saying 'project schema' while pointing to nx-schema.json. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the level-4 'minor instances' anchor.

3 / 5

Actionability

Every section gives fully executable, copy-paste-ready commands with real flags (--type, --withTarget, --affected --base=main, --uncommitted, jq filters over the --json output), and the 'Common Exploration Patterns' section maps common questions to concrete command pairs, including a practical grep fallback for the 'dependents' question Nx has no command for. Minor placeholders (my-app, @myorg/Y) are clearly illustrative, matching the top anchor's coverage of common cases.

5 / 5

Workflow Clarity

This is a read-only exploration skill, so no destructive/batch validation cap applies, and the 'Common Exploration Patterns' section provides clear question-to-commands sequences. It stops short of a 5 because some patterns are thin or indirect — e.g., 'Why is project X affected?' only suggests git diff plus checking X's root, which doesn't actually explain why X is affected (no nx graph/dep-graph step), and the discovery path (lockfile check for package manager) is mentioned only in passing without being woven into any workflow.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers (Listing Projects, Project Configuration, Targets, Workspace Configuration, Affected, Patterns) and no external bundle files exist, so there are no nested or buried references to penalize. It scores 4 rather than 5 because at ~180 lines some reference material — the exhaustive flag catalog and the key nx.json section notes — is inline where a references/ file (or the already-pointed-to nx schemas) would keep SKILL.md a leaner overview, and the repeated schema-pointer sentences blur the navigation slightly.

4 / 5

Total

16

/

20

Passed

Description

68%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 well-structured description with excellent explicit trigger guidance ('USE WHEN' plus natural example questions) and clear niche focus. Its main weakness is the 'what' clause: 'Explore and understand Nx workspaces' states the domain generically without naming the concrete capabilities (list projects, show resolved project config, find affected projects) that the body actually provides.

Suggestions

Replace the generic capability phrase with the concrete actions, e.g., 'List Nx projects, show resolved project configuration and targets, and find projects affected by changes' — this would lift specificity and completeness to the top anchors.

Add a few missing natural trigger terms such as 'monorepo' and file anchors like 'nx.json' / 'project.json' to round out keyword coverage.

Consider stating read-only intent in the description so it is distinguishable from skills that create or modify Nx projects.

DimensionReasoningScore

Specificity

The description's capability statement is just "Explore and understand Nx workspaces" — it names the domain but the actions are generic ('explore', 'understand') with no concrete capabilities like listing projects, showing resolved config, or finding affected projects. The rest of the text is trigger examples, not what the skill does, so it fits the anchor 'Names the domain but actions are minimal or generic' rather than the level-3 anchor which requires 1-2 concrete actions.

2 / 5

Completeness

Both parts are present: 'what' ("Explore and understand Nx workspaces") and an explicit, well-phrased 'USE WHEN' clause with concrete example questions — so it clears the level-4 anchor. It does not clearly reach level 5 because the 'what' is generic (explore/understand) rather than the concrete capability list the level-5 anchor shows ('Extract text and tables from PDF files, fill forms, merge documents').

4 / 5

Trigger Term Quality

Strong natural-language coverage via EXAMPLES ("What projects are in this workspace?", "How is project X configured?", "What's affected by my changes?", "Which projects depend on library Y?") plus trailing phrases ('Nx workspace structure, project configuration, or available tasks'). It falls just short of the level-5 anchor because a few natural terms users would say are missing — e.g., 'monorepo', 'targets/tasks to run on X', and file-anchored triggers like 'nx.json' or 'project.json'.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Nx workspace exploration) with distinct triggers ('nx workspace', 'projects in this workspace', 'affected by my changes'), and the examples are phrased as workspace-structure questions unlikely to be confused with build/run or general-monorepo skills. Minimal conflict risk.

5 / 5

Total

15

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nrwl/nx

Path

.cursor/skills/nx-workspace/SKILL.md

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.