CtrlK
BlogDocsLog inGet started
Tessl Logo

pnpm

Use when managing Node.js dependencies with pnpm - install packages, configure monorepo workspaces, set up pnpm catalogs, resolve dependency conflicts with overrides, patch third-party packages, and configure CI pipelines for pnpm projects

72

Quality

89%

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

86%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, actionable body that assumes Claude's competence and uses progressive disclosure effectively. Minor gains available from deduplicating the file listing and adding an error-recovery note for failed builds.

Suggestions

Merge the Reference Files table and Loading Files checklist into a single structure to remove the duplication of the same four file references.

Add a brief feedback loop to Verify Setup (e.g. 'if pnpm -r run build fails, run pnpm --filter <pkg> build to isolate the failing package').

DimensionReasoningScore

Conciseness

Lean and largely efficient with no concept over-explanation, but the Reference Files table and Loading Files checklist list the same four files, a minor redundancy that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands and config snippets (pnpm install/add, pnpm-workspace.yaml, package.json with workspace:/catalog: protocol) cover the common cases.

5 / 5

Workflow Clarity

The Verify Setup section provides a clear validation sequence (install, ls --depth 0, run build) for the batch workspace build, but no explicit error-recovery feedback loop is given.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to real bundle files (cli.md, workspaces.md, features.md, ci.md, all present in references/), content appropriately split, and explicit guidance not to load all files at once.

5 / 5

Total

18

/

20

Passed

Description

92%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, third-person description with an explicit 'Use when' trigger and a comprehensive list of concrete actions. Minor keyword synonyms could be added but it is highly specific and distinctive.

DimensionReasoningScore

Specificity

Lists six concrete actions ('install packages, configure monorepo workspaces, set up pnpm catalogs, resolve dependency conflicts with overrides, patch third-party packages, and configure CI pipelines'), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (managing Node.js dependencies with pnpm plus the action list) and 'when' via the concrete 'Use when managing Node.js dependencies with pnpm' trigger clause.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ('Node.js dependencies', 'pnpm', 'monorepo workspaces', 'catalogs', 'overrides', 'patch', 'CI pipelines') but a few plausible user phrases (e.g. 'migrate from npm/yarn', 'lockfile', 'outdated packages') are absent.

4 / 5

Distinctiveness Conflict Risk

The 'with pnpm' qualifier carves a clear, distinct niche with minimal overlap risk against generic npm/yarn dependency skills.

5 / 5

Total

19

/

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
onmax/nuxt-skills
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.