Content
30%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized but thin catalogue stub that redirects to an upstream repo, so it is structurally clean yet lacks actionable or sequenced guidance for the design-review task itself.
Suggestions
Replace the trivial 'open <url>' redirect with a concrete, copy-paste install step (e.g. the exact git clone / bundle path) so the skill can be acquired without manually hunting the upstream README.
Add a minimal inline workflow for the core task — the 0-10 rating dimensions and the AI Slop checklist — so the skill is usable without the upstream bundle, or explicitly document the fallback.
Drop the verbatim repeat of the frontmatter description in 'What it does' and tighten the 'catalogue entry advertises the skill' meta sentence to remove redundant tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and avoids explaining concepts Claude knows, but 'What it does' duplicates the frontmatter description verbatim and the 'catalogue entry advertises the skill...' framing is meta prose that could be tightened. | 2 / 3 |
Actionability | The only concrete command is 'open https://github.com/garrytan/gstack'; the actual design-review workflow is deferred upstream with no executable install steps, so it describes rather than instructs. | 1 / 3 |
Workflow Clarity | No sequenced steps exist for the skill's actual task (rating dimensions, AI Slop check); the body offers only a vague install-then-invoke acquisition hint with no detail on how to install the bundle. | 1 / 3 |
Progressive Disclosure | Well-organized into clear sections with a clearly signaled one-level reference to the upstream bundle; as an under-50-line skill it meets the simple-skills allowance for a top score on organization alone. | 3 / 3 |
Total | 7 / 12 Passed |