Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a thin catalogue entry that points to an upstream repo rather than teaching D3 directly. It is well-structured and lean but provides little in-place actionable or workflow guidance beyond a clone command, and repeats the frontmatter description.
Suggestions
Stop duplicating the frontmatter description in the 'What it does' section; reference it or summarize only what is not already in the frontmatter.
Add a brief verification step after cloning (e.g., confirm the skill appears in the agent's skills directory or loads by name) so the workflow has a checkpoint.
Include at least one minimal in-place D3 snippet or pointer to a specific upstream example file so the entry is actionable without cloning first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and does not explain D3 concepts Claude already knows, but it duplicates the frontmatter description verbatim in 'What it does' and carries catalogue meta-prose ('This catalogue entry advertises the skill in Open Design so the agent discovers it during planning'). | 2 / 3 |
Actionability | It provides a concrete executable command ('git clone https://github.com/jiannanya/snow-d3.git skills/snow-d3') but the actual chart-building guidance is deferred entirely to the upstream repo, leaving the skill's core task without in-place instruction. | 2 / 3 |
Workflow Clarity | An install sequence is present (inspect README, clone into skills/, invoke by name or trigger) but it is loose ('Inspect the upstream README for exact paths') with no verification that the skill loaded successfully. | 2 / 3 |
Progressive Disclosure | Under 50 lines with no local bundle files, organized into clear sections (What it does / Source / How to use) and a single one-level-deep external reference to the upstream repo, satisfying the simple-skill carve-out. | 3 / 3 |
Total | 9 / 12 Passed |