Content
51%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.
The body is a lean, well-organized catalogue stub, but its core promise — running the upstream workflow — rests on an undefined 'install the bundle' step with no executable command or verification. It reads as an advertisement rather than an actionable skill instruction.
Suggestions
Replace the 'open <url>' command with the actual executable install steps (e.g. 'git clone https://github.com/coreyhaines31/marketingskills && cp -r marketingskills/skills/marketing-psychology ~/.claude/skills/'), with exact paths stated instead of delegated to the upstream README.
Add a verification checkpoint after install, e.g. a command or check that the skill now appears in the agent's skill list before invoking it, to close the workflow's missing validation loop.
Drop the verbatim repetition of the frontmatter description in 'What it does' in favor of a one-line summary that adds information (e.g. what the upstream bundle contains).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short, assumes Claude's competence, and explains nothing Claude already knows. Not 5 because the 'What it does' section repeats the frontmatter description verbatim and 'Curated from Corey Haines' / OpenDesign catalogue narration is mild padding that could be trimmed; not 3 because there is no substantive over-explanation. | 4 / 5 |
Actionability | The only command is 'open https://github.com/...' (opens a browser, not an install step), and the actual instruction — 'install the upstream bundle into your active agent's skills directory' — is delegated with 'Inspect the upstream README for exact paths'. Not 3 because there is no executable step toward the skill's stated purpose at all (no install command, path, or invocation example); not 1 because a concrete URL and a named invocation path ('invoke this skill by name (`marketing-psychology`)') are given. | 2 / 5 |
Workflow Clarity | A rough sequence exists (open upstream repo → inspect README → install bundle → invoke by name or trigger phrase), but the critical install step is undefined and no validation that the skill is actually available follows. Not 3 because the pivotal step of the workflow ('install the upstream bundle') has no defined command or checkpoint; not 1 because the sequence that is present is coherent and correctly ordered. | 2 / 5 |
Progressive Disclosure | The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist), and per the rubric's simple-skill guidance it scores on well-organized sections — 'What it does', 'Source', 'How to use' are clear, and the single external pointer (the upstream URL) is one level deep and clearly signaled. Not 4 because nothing is inlined that belongs in a separate file and navigation is unambiguous. | 5 / 5 |
Total | 13 / 20 Passed |