Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a catalog stub that advertises and redirects to an upstream bundle rather than delivering functional skill content. It is organized and brief but offers no executable guidance, no real workflow, and no local progressive disclosure for the actual artifact-building task.
Suggestions
Replace the `open <url>` placeholder and "inspect the upstream README" deferral with concrete, copy-paste-ready install/usage commands so the body is actionable on its own.
Either inline a minimal Quick start with a working React/Tailwind artifact example, or ship local reference files under references/ that the body links to one level deep, instead of pointing off-repo to GitHub.
Remove the verbatim repetition of the description in "What it does" and the "Curated from..." filler to tighten conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and avoids explaining concepts Claude already knows, but it repeats the frontmatter description verbatim in the "What it does" section and carries promotional filler ("Curated from ComposioHQ awesome-claude-skills"), so it is "mostly efficient but could be tightened" rather than fully lean. | 2 / 3 |
Actionability | The only concrete-looking command is `open https://github.com/...` (a browser placeholder), and the real guidance is "inspect the upstream README" then "ask the agent to invoke this skill" — it describes rather than instructs, with no executable code or commands for the skill's actual artifact-building task, matching the level-1 anchor. | 1 / 3 |
Workflow Clarity | A loose sequence exists (inspect README → install bundle → invoke by name/trigger), but the steps are vague ("install the upstream bundle" with no concrete command) and lack any validation checkpoint, fitting the level-2 anchor of "steps listed but validation gaps; sequence present but checkpoints missing" rather than the fully specified level 3. | 2 / 3 |
Progressive Disclosure | Sections (What it does / Source / How to use) are organized, but there are no local bundle files (references/, scripts/, assets/ are absent) and all substantive content is deferred to an external GitHub URL rather than one-level-deep local references, so structure is present but the disclosure is not cleanly localized to the skill. | 2 / 3 |
Total | 7 / 12 Passed |