Content
47%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 short, well-sectioned catalogue stub that is token-efficient and honestly frames itself as an advertisement for the upstream bundle. Its substantive weakness is that it defers all real work to an external repo without providing any concrete install or invocation steps, so an agent reading it cannot act beyond opening a URL.
Suggestions
Replace the `open https://github.com/replicate/skills` hint with concrete, executable install commands (e.g., git clone with the actual repo URL and the copy/symlink path into the agent's skills directory).
Add a minimal quick-start example of invoking the skill (a sample prompt or API call) so the entry is actionable without leaving the file.
Remove the verbatim duplication of the frontmatter description in 'What it does' and drop the "> Curated from Replicate." line to tighten the token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no concept explanations, but the "What it does" section repeats the frontmatter description verbatim and the "> Curated from Replicate." line adds nothing — minor over-explanation that could be trimmed. Fits 'efficient; minor instances of over-explanation'. | 4 / 5 |
Actionability | The guidance says to "install the upstream bundle into your active agent's skills directory" but provides no install command (no git clone, no copy path), and the only code block is `open https://github.com/replicate/skills`, which is a navigation hint rather than an executable step. Fits 'minimal concrete guidance; high-level hints but missing the specific steps to execute'. | 2 / 5 |
Workflow Clarity | A rough two-step sequence is present (install upstream bundle, then invoke by name or trigger phrase), but the key step is undefined — no concrete install path, no example invocation, and no check that the bundle landed. Fits 'rough sequence present but many gaps; steps poorly defined'. | 2 / 5 |
Progressive Disclosure | Judged against the actual (empty) bundle structure: no references/, scripts/, or assets/ exist, and the body defers detail to a single well-signaled external reference (the upstream repo URL) with clean section headers. Good structure and easy navigation, but the actual skill content lives entirely outside the skill with no bundled reference files, leaving minor organization gaps. Fits 'good structure; most content appropriately placed; minor organization gaps'. | 4 / 5 |
Total | 12 / 20 Passed |