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

87%

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

100%

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

The body is a tight, fully actionable quick-reference with concrete executable commands and a real example. As a minimal single-purpose skill it satisfies conciseness, actionability, workflow clarity, and progressive disclosure.

DimensionReasoningScore

Conciseness

Extremely lean body with zero padding or redundant explanation; every token earns its place and it assumes Claude's competence.

3 / 3

Actionability

Provides fully executable commands ('npx nx list', 'npx nx add <plugin>') with a concrete copy-paste example ('npx nx add @nx/react').

3 / 3

Workflow Clarity

A simple single-purpose skill under 50 lines with two unambiguous actions and no destructive/batch operations requiring validation, so workflow clarity scores 3 per the simple-skills note.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references (none present), organized into a single clear section, meeting the simple-skills bar of 3.

3 / 3

Total

12

/

12

Passed

Description

75%

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 concise, uses third person, and clearly pairs a 'what' statement with an explicit 'USE WHEN' trigger clause. It is held back only by limited specificity and somewhat generic trigger-term coverage.

Suggestions

Enumerate more concrete actions in the description (e.g., 'discover, install, and configure Nx plugins') to raise specificity toward the score-3 anchor.

Add common natural-language variations or concrete examples (e.g., '@nx/react, @nx/vite') to broaden trigger-term coverage beyond generic 'framework or technology'.

DimensionReasoningScore

Specificity

Names the domain ('Nx plugins') and two actions ('Find', 'add') but not a comprehensive list of multiple specific concrete actions, matching anchor 2.

2 / 3

Completeness

Explicitly answers both what ('Find and add Nx plugins') and when via a clear 'USE WHEN' trigger clause enumerating the relevant scenarios.

3 / 3

Trigger Term Quality

Contains natural user phrasing like 'discover available plugins' and 'install a new plugin', but coverage is fairly generic ('framework or technology') without common variations or specific names.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Nx plugins) with distinct triggers tied to Nx tooling, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.