Content
86%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 tight, highly actionable instruction skill: correct non-obvious details (Nx project names, preserve-symlinks), copy-paste commands, and a sensible step order with an error-recovery branch. The residual gaps are a non-executable kill-process instruction and implicit rather than explicit validation (build success, server readiness) before proceeding.
Suggestions
Make the occupied-port handling executable: state the port (e.g. `lsof -ti :6006 | xargs kill -9`) or an equivalent concrete command instead of 'kill the old process'.
Add explicit validation checkpoints: verify the `yarn build` command exits successfully before starting Storybook, and wait for the 'Storybook started on' line in the output before sharing the URL.
Note where to find the URL/port if it is not printed in the startup output, so Step 4 is unambiguous even on a busy terminal.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative with zero padding; every line is actionable or carries genuinely non-obvious knowledge ("find its Nx project name in the project.json file... not the package.json name", NODE_OPTIONS="--preserve-symlinks"). This matches anchor 5 (every token earns its place), not anchor 4, since there is nothing to trim. | 5 / 5 |
Actionability | The build and start commands are concrete and copy-paste ready ("yarn build storybook <extra packages>", "NODE_OPTIONS=\"--preserve-symlinks\" yarn storybook:ui --no-open") with a worked example ("addon-review addon-vitest"), but the port-occupied branch ("kill the old process to free the port") gives direction rather than an executable command and no port number. Minor gaps place it at anchor 4 rather than the fully-executable coverage of anchor 5. | 4 / 5 |
Workflow Clarity | A clear five-step sequence with a confirm-first checkpoint (Step 1) and an error-recovery loop (occupied port → kill → restart) matches anchor 4. It falls short of anchor 5 because validation checkpoints are implicit: there is no explicit check that the build succeeded before starting, nor that Storybook is actually ready before giving the user the URL. | 4 / 5 |
Progressive Disclosure | There are no bundle files and none are needed; the body is under 50 lines and organized into clean, well-titled sections (one per step). Per the rubric's guidance for short skills with no external references, this matches anchor 5. | 5 / 5 |
Total | 18 / 20 Passed |