pnpm

Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces via pnpm-workspace.yaml, or managing dependencies with catalogs, patches, overrides, config dependencies, or the global virtual store.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pnpm/SKILL.md

The canonical home for this skill is pnpm in antfu/skills

Quality

Content

65%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 body is an excellent progressive-disclosure hub with lean, well-organized tables linking to verified reference files, plus a useful config-model note. Its weakness is actionability and workflow clarity: most executable detail lives in the referenced files rather than the body, and no explicit multi-step workflow is presented.

Suggestions

Add a short 'Quick start' or 'Common commands' section with 2-3 copy-paste pnpm commands (e.g., pnpm install, pnpm add, pnpm --filter) to raise inline actionability.

Move the version/date information (pnpm 10.x, 2026-06-22, v11 changes) into a clearly labeled 'Version notes' or 'Deprecated/old patterns' section to avoid penalizing conciseness.

For common multi-step tasks (e.g., setting up a workspace, applying a patch), include a brief numbered sequence with a validation checkpoint so the body itself carries workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with token-efficient tables and a genuinely useful config-model note, but the intro slightly over-explains concepts and the version/date blockquote contains time-sensitive info not placed in a deprecated section, fitting score-4 rather than 5.	4 / 5
Actionability	A few concrete directives exist ('Always use --frozen-lockfile (or pnpm ci) in CI', check pnpm-workspace.yaml), but the body is primarily a reference index pointing to other files rather than copy-paste executable guidance, matching score-3.	3 / 5
Workflow Clarity	The body organizes topics into coherent Core/Features/Best-Practices tables for navigation, but presents no explicit multi-step workflow or sequence with checkpoints, so it does not exceed score-3.	3 / 5
Progressive Disclosure	SKILL.md is a clear overview with three well-organized tables, each row linking one level deep to a real reference file (all 16 referenced files exist), matching the score-5 anchor for well-signaled one-level-deep references.	5 / 5
	Total	15 / 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.

The description is specific, complete, and distinctive, concisely stating what pnpm is and when to use it with concrete pnpm-specific trigger phrases. Minor gap: a few common natural synonyms (install, lockfile) are absent, capping trigger term quality at 4.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete capabilities (running commands, configuring workspaces via pnpm-workspace.yaml, managing catalogs/patches/overrides/config dependencies/global virtual store) with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	Clearly states the what ('Node.js package manager with strict dependency resolution') and an explicit when ('Use when running pnpm specific commands, configuring workspaces...'), matching the score-5 anchor for explicit what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	Good coverage of natural pnpm terms (pnpm specific commands, workspaces, pnpm-workspace.yaml, catalogs, patches, overrides), but missing common synonyms like install/add packages, lockfile, or .npmrc, so it falls below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear pnpm-specific niche with distinct triggers and minimal overlap risk with npm/Yarn, matching the score-5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: joe-bell/cva
Path: .agents/skills/pnpm/SKILL.md
Commit: 638844f

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.