Content
92%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.
An exemplary lean, single-purpose project skill: concrete commands, APIs, and paths in a well-ordered workflow with validation and a completion checklist. The only notable gap is that the key code example is a commented template for the `start()` body rather than executable code, offset by the explicit instruction to copy the water-cannon pattern.
Suggestions
Make the `CarnivalGame` example more concrete by either including a minimal runnable `start(canvas)` body (e.g., sizing from `theme.canvas` and one listener) or pointing to the specific part of `src/games/water-cannon/game.ts` that contains the working `start()` implementation to copy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every step is lean and imperative ("Kebab-case, short and plain, such as `ring-toss`", "Never use local storage directly"), with no explanation of concepts Claude already knows and no padding. Not a 4 because there are essentially no sentences that could be trimmed without losing information. | 5 / 5 |
Actionability | Concrete paths (`src/games/<game-id>/`, `src/games/index.ts`), exact commands (`npm run format`, `npm run check`), and exact API calls (`recordScore(ringToss.id, score)`, `canvasFont(...)`) make the guidance mostly executable. Not a 5 because the centerpiece code block's `start(canvas)` body is placeholder comments rather than runnable code (a template, justified by the pointer to water-cannon but still a gap). | 4 / 5 |
Workflow Clarity | Ten clearly sequenced steps with an explicit validation step ("Run `npm run format`, then `npm run check`"), a fix feedback loop ("fix anything it reports"), and a "Done when" checklist. Not a 4 because both checkpoints and an error-recovery loop are explicit, and the operations are non-destructive so no cap applies. | 5 / 5 |
Progressive Disclosure | The body is roughly 50 lines with well-organized sections (pattern pointer, Steps, Done when) and no bundle files to disclose; its only references are one-level pointers to real repo artifacts (`src/games/water-cannon/game.ts`, `src/carnival/theme.ts`). Not a 4 because nothing that belongs in a separate file is inlined and navigation is trivial. | 5 / 5 |
Total | 19 / 20 Passed |