Content
57%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 lean, well-organized catalogue stub that clearly redirects to the upstream bundle, scoring well on progressive disclosure. However, it provides little actionable guidance for the skill's actual purpose and no concrete install command or validation steps, capping actionability and workflow clarity at 2.
Suggestions
Replace the vague "install the upstream bundle into your active agent's skills directory" with the actual install command and exact target path so the setup is copy-paste ready.
Add at least a minimal inline quick-reference (e.g. Anthropic's primary hex values and font families) so the skill is actionable without always round-tripping to the upstream repo.
Drop the verbatim repetition of the frontmatter description in "What it does" and the meta line "A reference for shaping your own" to tighten conciseness toward 3.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and lean, but the "What it does" section repeats the frontmatter description verbatim and includes meta phrases ("Curated from Anthropic's official skills repository", "A reference for shaping your own"), so it is mostly efficient but could be tightened — the 2 anchor rather than the 3 anchor where every token earns its place. | 2 / 3 |
Actionability | It offers one concrete command ("open https://...") and a clear invoke-by-name instruction, but the central action ("install the upstream bundle into your active agent's skills directory") has no actual command and there is no executable guidance for applying brand colors/typology, matching the 2 anchor (some concrete guidance but incomplete, missing key details) rather than the fully executable 3 anchor or the purely descriptive 1 anchor. | 2 / 3 |
Workflow Clarity | A loose three-step sequence is present (inspect the upstream README, install the bundle, invoke by name or trigger), but the steps are vague and lack any validation checkpoints, fitting the 2 anchor (sequence present but checkpoints missing/implicit) rather than the 3 anchor's explicit validation steps. | 2 / 3 |
Progressive Disclosure | The body is under 50 lines and organized into clear sections (What it does, Source, How to use) with a single clearly-signaled one-level-deep external reference (the upstream GitHub URL); per the scoring notes, short well-organized skills with no need for local references can score 3, placing it above the 2 anchor's poorly-organized inline content. | 3 / 3 |
Total | 9 / 12 Passed |