pnpm

Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.

1.14x

Quality

66%

Does it follow best practices?

Impact

96%

1.14x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/pnpm/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its niche (pnpm) and provides explicit trigger guidance. Its main weakness is that the specific actions/capabilities could be more concrete—listing actions like 'install packages', 'configure monorepos', or 'resolve dependency conflicts' would strengthen it. Overall, it performs well on completeness and distinctiveness.

Suggestions

Add more concrete action verbs such as 'install packages', 'configure monorepos', 'resolve lockfile conflicts' to improve specificity beyond 'managing dependencies'.

Dimension	Reasoning	Score
Specificity	Names the domain (Node.js package manager) and mentions several specific features (workspaces, catalogs, patches, overrides), but doesn't list concrete actions like 'install packages', 'add dependencies', 'run scripts'. The actions are somewhat implied through 'configuring' and 'managing'.	2 / 3
Completeness	Clearly answers both 'what' (Node.js package manager with strict dependency resolution) and 'when' (Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides). Has an explicit 'Use when...' clause.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'pnpm', 'workspaces', 'dependencies', 'catalogs', 'patches', 'overrides'. Users asking about pnpm would naturally use these terms. Could benefit from mentioning 'pnpm-lock.yaml' or 'pnpm-workspace.yaml' but coverage is good.	3 / 3
Distinctiveness Conflict Risk	Clearly distinguishable from npm or yarn skills by explicitly naming 'pnpm' and pnpm-specific features like catalogs, patches, and overrides. The mention of 'strict dependency resolution' further differentiates it. Unlikely to conflict with other package manager skills.	3 / 3
	Total	11 / 12 Passed

Implementation

42%

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

The skill excels at progressive disclosure with a clean, well-organized table-of-contents structure pointing to reference files. However, it lacks any actionable content — no quick-start commands, no executable examples, and no concrete workflow steps in the overview itself. The opening paragraph wastes tokens explaining what pnpm is, which Claude already knows.

Suggestions

Add a Quick Start section with 3-5 essential pnpm commands (e.g., `pnpm install`, `pnpm add <pkg>`, `pnpm run <script>`) as executable examples.

Remove or drastically shorten the opening paragraph explaining what pnpm is — Claude already knows this. Keep only the actionable guidance (check for pnpm-workspace.yaml, use --frozen-lockfile).

Add a brief workflow for common multi-step operations, such as adding a dependency in a workspace or patching a package, with validation steps.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what pnpm is and how it works (content-addressable store, deduplication, phantom dependencies) — Claude already knows this. The 'Important' callout is reasonable but slightly verbose. The reference tables themselves are lean and well-structured.	2 / 3
Actionability	The skill body contains zero executable commands, code snippets, or concrete examples. It is entirely a directory of references with descriptions. There's no quick-start command, no example of running pnpm install, no copy-paste ready guidance whatsoever.	1 / 3
Workflow Clarity	There's a hint at workflow ('check for pnpm-workspace.yaml and .npmrc', 'use --frozen-lockfile in CI') but no sequenced steps, no validation checkpoints, and no feedback loops. For a skill covering workspaces, patches, and CI/CD, the lack of any multi-step workflow in the overview is a gap, though the content may exist in references.	2 / 3
Progressive Disclosure	The skill is well-organized as a concise overview with clearly categorized tables pointing to one-level-deep reference files. Topics are logically grouped into Core, Features, and Best Practices sections with descriptive summaries and clear navigation paths.	3 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: antfu/skills
Commit: 50deaeb

Reviewed: 26 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.