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.
A strong, executable implementation checklist with a clear numbered workflow, per-step validation in the setup steps, and a final validation plus user-test section. The main defects are a dangling reference to a nonexistent reference/cosmos-config.md file (twice), some repeated version/config content, and a thin troubleshooting section.
Suggestions
Add the referenced reference/cosmos-config.md file (or remove both links to it) so the advertised ProfileConfig/operator_args details actually exist in the bundle.
Deduplicate the Cosmos 1.11.0 version note (frontmatter note, intro, and step 1 all restate it) and have Option A reference the configs from steps 4–6 instead of re-inlining them.
Expand the Troubleshooting section: explain what AIRFLOW__COSMOS__PRE_DBT_FUSION=1 does and add a diagnose-fix-retry loop instead of a bare env-var snippet.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is directive rather than explanatory — tables of constraints, code, and validation steps with no padding about what dbt/Cosmos/Airflow are. Minor over-explanation and repetition remain: the Cosmos 1.11.0 version note appears three times (frontmatter note, intro, step 1) and Option A re-inlines the profile/execution configs already shown in steps 4–5, which fits the efficient-with-minor-trimmables anchor rather than the every-token-earns-its-place anchor at 5. | 4 / 5 |
Actionability | Guidance is fully executable: `pip install "astronomer-cosmos>=1.11.0"`, a concrete Dockerfile install with `curl -fsSL https://public.cdn.getdbt.com/fs/install/install.sh | sh -s -- --update`, common install paths, and complete copy-paste-ready DbtDag and DbtTaskGroup examples covering both common integration cases. The bare `AIRFLOW__COSMOS__PRE_DBT_FUSION=1` troubleshooting snippet is a very minor gap that does not undermine the otherwise executable coverage. | 5 / 5 |
Workflow Clarity | Steps 1–8 are clearly numbered and sequenced, steps 1 and 2 carry explicit `**Validate**` checkpoints, and step 8 consolidates a final checklist plus "User Must Test" items. It falls short of the anchor-5 explicit feedback-loop pattern because steps 3–7 have no inline checkpoints and the troubleshooting section offers a single unexplained env var rather than a diagnose-fix-retry loop. | 4 / 5 |
Progressive Disclosure | The body twice points to "reference/cosmos-config.md" with clear signaling, but no bundle directory exists and that referenced file is absent, so the content split it advertises is not real and navigation dead-ends. The inline body itself is well-sectioned, so this fits the some-structure-with-flawed-references anchor rather than the minimal-structure anchor at 2 or the good-structure anchor at 4. | 3 / 5 |
Total | 16 / 20 Passed |