Content
65%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.
A highly actionable, well-sectioned command reference whose main weaknesses are the Quick Reference/Core Commands duplication, missing validation guidance around destructive repo/cache/endpoint operations, and two clearly signaled reference files that are absent from the bundle.
Suggestions
Remove the duplication between the 'Quick Command Reference' table and 'Core Commands' (or drop the table and keep the annotated command blocks) to reclaim tokens.
Add a short validation note for destructive/batch operations, e.g. run `hf repo-files list` or `hf cache ls` before `delete`/`rm`, and confirm `hf auth whoami` before uploads.
Ship the referenced bundle files (references/commands.md, references/examples.md) or remove the References section, and move the exhaustive command/GPU-flavor listings into them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient — the body is dense command lists with no concept explanations Claude already knows — but the ~20-row 'Quick Command Reference' table duplicates the 'Core Commands' section almost entirely, and 'Check Cache Usage' repeats `hf cache ls`/`hf cache rm` already shown. This matches anchor 3 ('could be tightened'); not 2, since there is no padded prose or unnecessary explanation, just structural duplication. | 3 / 5 |
Actionability | Every section gives fully executable, copy-paste-ready commands with realistic flag combinations (`hf download <repo_id> --local-dir ./models`, `hf upload <repo_id> . . --create-pr`, the fully-specified `hf endpoints deploy` with region/vendor/instance flags), and 'Common Patterns' covers the common cases. Matches anchor 5; placeholders like `<repo_id>` are standard CLI notation, not pseudocode. | 5 / 5 |
Workflow Clarity | Multi-step patterns are present (publish: `repo create` → `upload` → `tag create`), but the skill documents destructive and batch operations — `hf repo delete`, `hf repo-files delete "*.txt"`, `hf cache rm`, `hf endpoints delete --yes` — with no verification or feedback-loop steps (e.g., confirm what a delete will remove, or verify an upload landed), which caps workflow clarity at 3 per the judging guidelines. Not 2: sequences that exist are correct and clearly shown. | 3 / 5 |
Progressive Disclosure | Section structure is good and two references are clearly signaled ('Complete command reference: See references/commands.md'), but no references/ directory exists in the bundle — both pointers are dangling — and the inline 'Core Commands' material overlaps what the missing commands.md would presumably hold. This fits anchor 3 (structure present, but reference placement/content split is not verifiable or appropriately divided); not 4, because scored against the actual bundle structure the references do not resolve. | 3 / 5 |
Total | 14 / 20 Passed |