CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a well-structured navigation/overview skill that excels at progressive disclosure and conciseness. Its main weakness is the lack of concrete, executable examples or quick-start workflows in the top-level document — it reads more like a table of contents than an actionable skill. Adding a brief quick-start section with common commands would significantly improve actionability.

Suggestions

Add a 'Quick Start' section with 2-3 copy-paste ready commands (e.g., `pnpm install`, `pnpm add <pkg>`, `pnpm run <script>`) to improve actionability.

Include a brief workflow for the most common task (e.g., setting up a new pnpm project or migrating from npm) with explicit steps and validation checkpoints.

DimensionReasoningScore

Conciseness

The content is lean and efficient. The introductory paragraph is brief but adds value by highlighting pnpm's unique characteristics (content-addressable store, strict resolution). The configuration model callout is genuinely useful context that Claude wouldn't inherently know. The version note is appropriately placed. Tables are compact and informative.

3 / 3

Actionability

The skill provides some concrete guidance (e.g., 'Always use --frozen-lockfile or pnpm ci in CI', check pnpm-workspace.yaml for settings, .npmrc only for auth) but lacks executable code examples or copy-paste ready commands. It's primarily a navigation document pointing to references rather than providing directly actionable instructions.

2 / 3

Workflow Clarity

The configuration model paragraph provides a clear mental model for where settings live, which is helpful. However, there are no explicit multi-step workflows, validation checkpoints, or sequenced processes in the main skill body. For a tool that involves migration, CI setup, and patching (all multi-step), the top-level skill could benefit from at least one quick-start workflow.

2 / 3

Progressive Disclosure

Excellent progressive disclosure structure. The skill is organized into clear categories (Core, Features, Best Practices) with well-labeled tables providing topic, brief description, and one-level-deep references to specific files. Navigation is intuitive and references are clearly signaled with consistent naming conventions.

3 / 3

Total

10

/

12

Passed

Description

100%

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 strong skill description that clearly identifies pnpm as the target tool, lists specific capabilities and features, and includes an explicit 'Use when' clause with well-chosen trigger terms. The description is concise yet comprehensive, covering pnpm's distinctive features like workspaces, catalogs, patches, and the global virtual store, making it easily distinguishable from other package manager skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and features: 'strict dependency resolution', 'pnpm specific commands', 'configuring workspaces via pnpm-workspace.yaml', 'managing dependencies with catalogs, patches, overrides, config dependencies, or the global virtual store'.

3 / 3

Completeness

Clearly answers both 'what' (Node.js package manager with strict dependency resolution) and 'when' (explicit 'Use when' clause covering pnpm commands, workspace configuration, and specific dependency management features).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'pnpm', 'pnpm-workspace.yaml', 'workspaces', 'catalogs', 'patches', 'overrides', 'global virtual store', 'dependency resolution'. These are terms a developer would naturally use when needing pnpm help.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — pnpm-specific terminology like 'pnpm-workspace.yaml', 'catalogs', 'global virtual store', and 'pnpm specific commands' clearly distinguish this from npm or yarn skills. Very low conflict risk.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
antfu/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.