CtrlK
BlogDocsLog inGet started
Tessl Logo

nx-plugins

Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.

92

1.25x
Quality

88%

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

The content is minimal, executable, and well-organized for a simple skill, with copy-paste commands and a worked example. The only gap is the absence of any post-install verification step.

Suggestions

Add a brief verification step after install, e.g. confirm the plugin registered its generators with `npx nx list <plugin>` or note that the user should be prompted to restart/verify.

Optionally mention how to remove or update a plugin so the common lifecycle actions are complete.

DimensionReasoningScore

Conciseness

The body is two lean bullets with executable commands and one example, assuming Claude's competence and adding no padding or background concepts.

5 / 5

Actionability

It gives copy-paste-ready commands (`npx nx list`, `npx nx add <plugin>`) plus a concrete example (`npx nx add @nx/react`) covering the common list and install cases.

5 / 5

Workflow Clarity

The two actions are clearly presented and naturally ordered (list to discover, then add to install), but there is no verification checkpoint confirming a plugin was actually installed/registered, leaving a minor validation gap.

4 / 5

Progressive Disclosure

This is a sub-50-line single-purpose skill with no need for external references, and its single well-organized section with two bullets meets the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

82%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.

The description is third-person, concise, and cleanly answers both what the skill does and when to invoke it, with concrete trigger phrases. Its only weakness is modest action specificity beyond the find/add verbs.

Suggestions

Expand the 'what' with one or two more concrete verbs (e.g., 'list, install, and configure Nx plugins') to lift specificity beyond the two-action baseline.

DimensionReasoningScore

Specificity

"Find and add Nx plugins" names the domain and two concrete actions (find, add) but offers no further granularity, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It explicitly states what the skill does ("Find and add Nx plugins") and when to use it ("USE WHEN user wants to discover available plugins, install a new plugin, or add support..."), answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

The USE WHEN clause supplies natural phrases users would say ("discover available plugins", "install a new plugin", "add support for a specific framework or technology"), giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

"Nx plugins" carves out a clear niche with distinct triggers tied to the Nx toolchain, giving minimal conflict risk with unrelated skills.

5 / 5

Total

17

/

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
leboncoin/spark-web
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.