Content
80%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable skill that covers all major package managers with concrete, executable commands and expected outputs. Its main weakness is the workflow section, which lists steps but lacks explicit verification commands and feedback loops for error recovery—important given the skill's purpose of fixing resolution errors. Conciseness is strong though a few explanatory notes could be trimmed.
Suggestions
Add a concrete verification step to the workflow, e.g., `ls -la packages/app/node_modules/@org/ui` or `node -e "require('@org/ui')"` to confirm the symlink works.
Expand the 'Debug Cannot find module' example into a proper feedback loop: verify → fix → re-install → verify again, with specific commands for each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with minimal fluff. The 'Detect Package Manager' section is useful context Claude might not always have. Minor verbosity in the Notes section (e.g., explaining hoisting differences) but generally every section earns its place. The one-liner 'npm resolves to local workspace automatically during install' is slightly redundant but not egregious. | 4 / 5 |
Actionability | Fully executable, copy-paste ready commands for all four package managers with concrete examples showing both the command and the resulting package.json. The filter/workspace flags are specific and correct. Multiple usage patterns are covered (from consumer dir, with --filter, etc.). | 5 / 5 |
Workflow Clarity | The 4-step workflow is listed but step 4 ('Verify symlinks created in consumer's node_modules/') lacks a concrete verification command. The 'Debug Cannot find module' example in Example 3 provides a basic troubleshooting sequence but no explicit validation/feedback loop. For a skill that addresses resolution errors and linking issues, a concrete verification step (e.g., checking the symlink exists, running a build to confirm) would strengthen this. | 3 / 5 |
Progressive Disclosure | For a skill of this size (~80 lines) with no need for external references, the content is well-organized with clear section headers, horizontal rules separating package managers, and a logical flow from detection → workflow → per-manager syntax → examples → notes. No bundle files are needed. | 5 / 5 |
Total | 17 / 20 Passed |