Content
63%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 concrete, well-structured design spec with a clearly ordered reproduction protocol, weakened by its dependency on an example.html that is not shipped in the bundle and by token values duplicated between the spec sections and the do/don't table. Adding a final verify-against-example step and shipping (or removing the dependency on) the canonical file would lift it substantially.
Suggestions
Ship example.html in the skill folder (or inline its structure), since Steps 1–2 mandate mirroring its DOM hierarchy and class names but the file is absent from the bundle.
Add a final validation step to the protocol — e.g., 'Compare your output structure against example.html before finishing' — to close the workflow loop.
Deduplicate the do/don't table: it repeats the shadow token, font stack, status hues, and row-height rules already specified above; reference those sections instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific values (no explaining of known concepts), but the do/don't table restates the shadow token, font stack, status hues, and row heights nearly verbatim from earlier sections, and the full token block duplicates what the canonical example.html already defines. Meaningful tightening is possible. | 3 / 5 |
Actionability | Highly concrete guidance for a design skill: exact hex values ("accent: #5e6ad2"), pixel dimensions ("left nav 240px", "row height ~36px"), and an explicit row layout pattern. Not 5 because the core instruction — mirror example.html "1:1" including DOM hierarchy and class names — cannot be executed as written: example.html is not present in the bundle. | 4 / 5 |
Workflow Clarity | Clear ordered three-step protocol ("Step 1... read the shipped example.html... Step 2... Mirror the example's structure 1:1... Step 3... refresh mock values") with explicit prohibitions acting as inline guardrails. Not 5 because there is no final validation step comparing the produced output against example.html. | 4 / 5 |
Progressive Disclosure | Section structure within SKILL.md is clear and scannable, and the single external reference (example.html) is prominently signaled in Step 1. However, that referenced path does not exist in the bundle, and the full token/palette reference material is inlined rather than kept alongside the canonical example. | 3 / 5 |
Total | 14 / 20 Passed |