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.
52
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at progressive disclosure with well-organized reference tables, but lacks actionability - it's essentially a table of contents without any executable examples or concrete commands in the main body. The introductory content explains concepts Claude already knows, and there are no workflow examples showing how to actually use pnpm for common tasks.
Suggestions
Add a Quick Start section with 3-5 executable pnpm commands (e.g., `pnpm install`, `pnpm add -D`, `pnpm --filter`) that demonstrate core usage
Remove or significantly trim the explanatory paragraph about what pnpm is and how content-addressable storage works - Claude knows this
Add a concrete workflow example for a common task like 'adding a dependency to a workspace package' with validation steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The intro paragraph explains what pnpm is and how it works (content-addressable store, deduplication), which Claude already knows. The version note and general description add tokens without actionable value. | 2 / 3 |
Actionability | No executable code or concrete commands are provided in the main skill body. It only describes topics and points to references without any copy-paste ready examples or specific guidance. | 1 / 3 |
Workflow Clarity | The Important note mentions checking config files and using --frozen-lockfile, but there's no sequenced workflow, validation steps, or error recovery guidance for common pnpm operations. | 2 / 3 |
Progressive Disclosure | Excellent organization with clear tables categorizing topics into Core, Features, and Best Practices. References are one level deep with descriptive links and well-signaled navigation. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.