Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, highly actionable body: executable commands for every manager, expected results, and hoisting caveats Claude would not reliably know. It loses points for duplicated examples, a missing verification-failure recovery path, and slight redundancy.
Suggestions
Remove Examples 1 and 2 (they repeat the pnpm and npm commands verbatim from the per-manager sections) and keep only the debug example, or replace them with scenarios not already covered such as yarn v1 or private registry workspaces.
Add a short failure-recovery step after the workflow's verification step, e.g., 'If the symlink is missing, run the manager's install command from the repo root and re-check; if still missing, confirm the workspace globs in the root package.json cover the provider package.'
State how to declare workspaces in the root package.json (the 'workspaces'/'workspaces:*' globs), since the Notes section assumes them and a missing root declaration is a common cause of failed linking.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The per-manager sections are lean and command-first with expected package.json results, but the Examples section (Examples 1 and 2) re-pastes commands already shown verbatim in the pnpm and npm sections, so those tokens do not earn their place. | 4 / 5 |
Actionability | Fully executable copy-paste commands for all four package managers, a lockfile-based detection table, expected dependency entries after each command, and a concrete debug example covering the common failure case. | 5 / 5 |
Workflow Clarity | The workflow lists a clear 4-step sequence that includes verification ('Verify symlinks created in consumer's node_modules/') and the debug example acts as a recovery loop, but there is no guidance for what to do when verification fails (e.g., symlink missing after install). | 4 / 5 |
Progressive Disclosure | Well-sectioned, easily navigable single file with no bundle files to reference; content is mostly appropriately placed, though at ~120 lines with duplicated example commands it could be tightened rather than split. | 4 / 5 |
Total | 17 / 20 Passed |