Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with a clear, validated workflow, but it is a long monolithic file that could offload reference material to bundle files and trim API-internal explanations.
Suggestions
Trim the 'What Happens Server-Side' virality-framework taxonomy to a one-line summary, since the API handles it and the agent does not act on those internals.
Split the full output schema and server-side pipeline detail into a reference file under references/ and link to it, so SKILL.md stays an overview.
Add the missing scripts/run-ai-clipping.sh bundle file (or fix the inconsistent path library/edit/ai-clipping/scripts/...) so referenced paths resolve.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with actionable tables and commands, but the eight-item 'What Happens Server-Side' virality taxonomy is explanatory detail the API handles internally and could be tightened; not a 3 because not every token earns its place. | 2 / 3 |
Actionability | Provides copy-paste-ready executable bash commands, a concrete input table, named CLI flags, and a full output schema — matching 'fully executable code/commands; copy-paste ready'. | 3 / 3 |
Workflow Clarity | Sequences Collect Inputs → Verify Prerequisites → Run, with prerequisite validation in Step 2, error-recovery guidance in 'Failure Modes', and a 'Done Criteria' checklist providing explicit checkpoints and feedback loops. | 3 / 3 |
Progressive Disclosure | Well-sectioned but monolithic: the skill is ~185 lines (above the 50-line simple-skill exception), no bundle/reference files exist, and the referenced run-ai-clipping.sh script does not resolve to a real file, with reference-grade content (server-side taxonomy, full output schema) kept inline. | 2 / 3 |
Total | 10 / 12 Passed |