Content
92%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.
An exemplary operational skill body: dense with non-obvious project facts, clearly sequenced with validation and destructive-operation guards, and a clean one-level-deep reference split. The single dimension below 5 (actionability) reflects deliberate, justified delegation of exact commands to the bundle's own files rather than a real flaw.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every sentence carries project-specific, non-inferable facts ("TCP 80/443 and UDP 443 must reach Caddy", "the Kratos cipher secret length", ".env.release pins that revision's images by digest", "Talos OSS does not emit traces") with no generic concept explanation. The recurring secrets guidance appears at three distinct phases as checkpoints rather than padding, so the body earns anchor 5 rather than anchor 4's trimmable over-explanation. | 5 / 5 |
Actionability | It provides one copy-paste command ("docker compose --env-file .env config --quiet") plus exact file names, paths, and URLs, but most executable detail (Compose up command, verification commands, backup procedure) is delegated to the bundled README and references/verification.md. The delegation is explicitly justified by version drift ("do not carry forward image versions from this skill"), which keeps it above anchor 3, but it is not the fully self-contained, copy-paste-ready coverage of anchor 5. | 4 / 5 |
Workflow Clarity | A clearly sequenced process (inspect host → select release/source path → verify checksums → configure .env → config check → start → verify endpoints → optional ops → report) with explicit validation checkpoints (checksum and SHA256SUMS verification, config --quiet before startup, the verification path, backup/restore testing) and an error-recovery loop ("If startup fails, inspect only the affected service's status and bounded logs"). Destructive risk is explicitly guarded ("Do not run `down -v` on a deployment with data"), so the destructive-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview and the one bundle file, references/verification.md, is referenced twice with clearly signaled links (including the resolving #source-checkout-rehearsal anchor); the verification detail lives one level deep with no further nesting. Content is appropriately split between decisions/constraints in the body and verification commands in the reference, matching anchor 5. | 5 / 5 |
Total | 19 / 20 Passed |