Content
82%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 tight, information-dense skill for the Pika H3 Flex API: concrete parameters, explicit cost/validation behavior, and thorough error recovery with no padding. The main gaps are the absence of a worked example call or prompt and no consolidated end-to-end workflow narrative.
Suggestions
Add one fully worked example — a sample `pika_video` request plus the filled-in shot-list prompt it would use — so the five-part prompting structure has a concrete model to copy.
Consolidate the workflow into an explicit ordered sequence (draft at 480p → `dry_run` preflight → generate → check `data.cost_status` is `settled` → rerun approved take at delivery resolution) instead of distributing it across sections.
Consider moving the full per-resolution price tables and detailed reference rules into a `references/` file, keeping SKILL.md as a leaner overview with cost decision rules inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with Pika-specific operational facts (parameter enums, frame-grid rounding, per-resolution pricing, error codes) and never explains concepts Claude already knows; e.g. 'Output rounds up to the model's frame grid (124 frames for a 5 second request at 24 fps)' and 'honor `data.retry_after`, then submit again'. Every section carries non-inferable API detail, matching the 'every token earns its place' anchor. | 5 / 5 |
Actionability | Parameter names, enums, defaults, and constraints are fully specified ('Set `dry_run: true` to validate the request', 'Call `pika_video` again with that object (and a longer `poll_timeout`)'), and the five-part prompt structure is concrete. It falls short of anchor 5 only because there is no worked example — no sample `pika_video` invocation or filled-in prompt showing the shot-list format in practice. | 4 / 5 |
Workflow Clarity | Validation checkpoints and feedback loops are present: `dry_run` preflight with quoted price, per-error recovery actions (`insufficient_balance`, `rate_limited` with `retry_after`, `resume_job` on poll timeout), and a draft-at-480p-then-rerun-at-delivery-resolution path. It sits below anchor 5 because these steps are distributed across sections rather than consolidated into one explicit end-to-end sequence. | 4 / 5 |
Progressive Disclosure | The single file (~108 lines) is well-organized with clear sections (Route and billing, Operations, Reference rules, Shared parameters, Prompting, Failure handling, Provenance) and no nested references. It does not reach anchor 5 because the body exceeds the under-50-lines simple-skill case and the full pricing/rate tables and prompting guide could arguably live in reference files, though nothing is misfiled or buried. | 4 / 5 |
Total | 17 / 20 Passed |