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 content is highly actionable with executable commands, a precise output contract, and well-structured sections, but it is undermined by a dead reference to a RECIPES.md file that is not present in the bundle. Conciseness and workflow sequencing are solid with minor room to tighten.
Suggestions
Add the missing RECIPES.md file (referenced in the closing line and in the --json flag entry as RECIPES.md#structured-output), or remove those references — broken links promise navigation that does not exist.
Collapse the install, preflight, and run steps into a single numbered checklist with an explicit validate-then-run feedback loop (e.g. 'if preflight fails, run fractal config setup / fix Docker, then re-check') to make the workflow sequence and recovery path explicit.
Trim the 'When to reach for it' section, which largely restates the frontmatter description, to reduce redundancy and reclaim token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and assumes competence, but the 'When to reach for it' section overlaps heavily with the frontmatter description and the RLM-mechanism explanation is slightly more than needed, so a few lines could be trimmed. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready guidance throughout: an install one-liner, `fractal -p "..." --workspace /path`, preflight checks, a complete output-contract table with exit codes, and concrete flag syntax like `out=$(fractal -p "..." 2>err.log)`. | 5 / 5 |
Workflow Clarity | A clear install → preflight → run → check-exit-code sequence exists with a validation checkpoint (`fractal config status`, `docker info`), but the steps are distributed across sections rather than presented as one explicit checklist, and there is no fix-and-retry feedback loop for failed runs. | 4 / 5 |
Progressive Disclosure | Sections are well organized and the body signals a one-level-deep reference to RECIPES.md for advanced recipes, but that referenced file (cited twice, including `RECIPES.md#structured-output`) does not exist in the bundle, so the promised navigation is broken. | 3 / 5 |
Total | 16 / 20 Passed |