CtrlK
BlogDocsLog inGet started
Tessl Logo

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

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-organized, highly actionable command reference for Nx workspace exploration that assumes Claude's competence and offloads affected-project detail to a real reference file. Minor deduplication of the recurring 'nx show projects' examples would tighten it further.

Suggestions

Consolidate the recurring 'nx show projects' examples that appear in Listing Projects, Common Exploration Patterns, and Programmatic Answers into a single section to reduce duplication.

Consider moving the longer Programmatic Answers example JSON blocks into a reference file so the main SKILL.md stays a tighter overview with one-level-deep detail.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no explaining of basic Nx concepts, but commands like 'nx show projects' recur across Listing Projects, Common Exploration Patterns, and Programmatic Answers sections, adding mild duplication that could be tightened.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands with jq pipelines covering the common cases (list projects, inspect targets, query the project graph, troubleshoot), plus concrete example JSON output.

5 / 5

Workflow Clarity

Content is clearly organized by user question type with a Troubleshooting section giving rough diagnostic sequences; as a read-only exploration skill it needs no validation checkpoints, but the workflows are pattern-based rather than strictly sequenced with explicit feedback loops.

4 / 5

Progressive Disclosure

Structure is good with clear section headers and one well-signaled, one-level-deep reference (references/AFFECTED.md, verified present) for affected-project detail; the main body is an appropriate inline command reference, though it is fairly extensive.

4 / 5

Total

17

/

20

Passed

Description

90%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 explicit what/when guidance and highly natural trigger examples scoped to Nx workspaces. The only weakness is the generic lead verb 'Explore and understand', which keeps specificity from the top anchor.

DimensionReasoningScore

Specificity

It names the Nx domain and a couple of concrete actions ('answering questions about the workspace, projects, or tasks', 'check available targets/configuration'), but the lead verb 'Explore and understand' is generic, so coverage is not comprehensive.

3 / 5

Completeness

It explicitly answers both what ('Explore and understand Nx workspaces') and when ('USE WHEN ...', 'ALSO USE WHEN ...') with concrete trigger phrases and example queries.

5 / 5

Trigger Term Quality

The EXAMPLES list natural user phrases ('What projects are in this workspace?', 'What depends on library Y?', 'Cannot find configuration for task', 'debug nx task failure') giving comprehensive coverage of how users actually ask.

5 / 5

Distinctiveness Conflict Risk

The Nx-specific domain and trigger terms (nx command failure, targets, configuration, project graph) carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getlarge/themoltnet
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.