Content
78%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 highly actionable and information-dense, with a clean install→preflight→run structure and an excellent output/exit-code contract. Its main weaknesses are a broken main reference (RECIPES.md is cited twice but missing from the bundle), a duplicated stream-capture snippet, and the absence of an explicit failure-recovery loop.
Suggestions
Ship RECIPES.md alongside SKILL.md (or inline its four patterns) — the body twice defers to a file that is not present in the bundle, leaving the CI-gate, multi-turn-driver, diff-review, and structured-output recipes unreachable.
De-duplicate the stream-capture guidance: `out=$(fractal -p "..." 2>err.log)` appears in both Quick start and Output contract; state it once and cross-reference.
Add an explicit remediation loop after the output contract, e.g., exit 1 → check `fractal: failed:` on stderr and re-run preflight; exit 2 → `--resume <session_id>` or re-run with a higher `--max-iterations`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with tool-specific facts Claude cannot know (exit codes, flag semantics, output contract) and avoids explaining known concepts, but the stream-capture snippet `out=$(fractal -p "..." 2>err.log)` is duplicated in both Quick start and Output contract, and the RLM rationale paragraph partly repeats the frontmatter. Efficient with minor trimming opportunities — not the lean 5 anchor. | 4 / 5 |
Actionability | Fully executable throughout: a copy-paste install one-liner, preflight commands with non-interactive fallbacks (`fractal config set`, env vars), a precise quick-start invocation, an exit-code contract, and exact flag syntax including stdin piping and session-resume details. | 5 / 5 |
Workflow Clarity | The sequence is clear and ordered (check/install → preflight Docker and config → run → interpret streams/exit codes) with checkpoints and error-interpretation guidance, but there is no explicit run→check-exit-code→remediate loop (e.g., exit 2 → resume or raise --max-iterations) tying the pieces together. | 4 / 5 |
Progressive Disclosure | References are clearly signaled and one level deep ([RECIPES.md](RECIPES.md) with an anchor link), but the referenced file does not exist anywhere in the skill bundle, so the deferred content (CI gate, multi-turn driver, diff review, structured output) is unreachable — navigation breaks at the main reference. | 3 / 5 |
Total | 16 / 20 Passed |