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, self-contained skill: it gives fully executable guidance for both the hosted Chromatic and self-hosted test-runner paths, with a useful decision table and realistic CI gotchas. Weaknesses are minor — duplicated serve-and-test instructions and no baseline-update recovery flow when snapshots legitimately change.
Suggestions
Deduplicate the Storybook serve-and-test flow: keep the detailed bash sequence in one place (Running or CI integration) and reference it from the other to trim roughly 15 lines.
Add a short 'Updating baselines' note for Path 2 covering how to regenerate snapshots after intentional UI changes (e.g., test-storybook --update-snapshots) so CI failures have a recovery loop.
Consider moving the full GitHub Actions YAML into a reference file to keep SKILL.md as a lean overview, since the workflow is already summarized by the concurrently/wait-on guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows and uses tables efficiently (hooks, path comparison), but the serve-and-test flow is duplicated between the 'Running' bash block and the 'CI integration' YAML, and phrases like 'This is the default recommendation in the docs' are editorial padding. | 4 / 5 |
Actionability | Every step is copy-paste ready: install commands, the package.json script, a complete .storybook/test-runner.ts config with opt-out handling, run commands, and a full GitHub Actions workflow covering the common cases for both paths. | 5 / 5 |
Workflow Clarity | Both paths are clearly sequenced (install, activate/config, run, CI) with practical checkpoints like 'wait-on ... will fail unhelpfully' and 'without -k, the workflow hangs'. The missing piece is an error-recovery flow for intentional UI changes (e.g., updating baselines via --update-snapshots), which keeps it below a 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the skill is well-sectioned, correctly delegating Chromatic CLI and toHaveScreenshot details to sibling skills rather than duplicating them. The ~245-line single file with a 40-line inlined CI workflow could be split into a reference file, which leaves minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |