Content
77%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 with a well-sequenced, validation-backed workflow and concrete tool calls and payloads. Its weak spots are conciseness (a redundant Important notes section) and progressive disclosure (a referenced sync-types.md file that is missing from the bundle).
Suggestions
Remove or fold the "Important notes" section into the relevant workflow steps — it re-states webhook/prefix/connect-link/validate-before-create guidance already covered above.
Create the referenced `./references/sync-types.md` (currently absent) or inline its full sync-type decision rules so the dangling link does not break navigation.
Tighten the Pre-flight credential-gotchas list by moving per-source key-type trivia (Resend, Mailgun, RevenueCat, etc.) into a reference file, keeping only the highest-impact gotchas inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is operational and tool-specific (credential gotchas, webhook flow) and earns its place, but the "Important notes" section restates webhook-as-separate-step, prefix-is-load-bearing, prefer-connect-link, and validate-before-create guidance already detailed in the workflow steps, adding noticeable repetition. | 3 / 5 |
Actionability | Provides named tool calls with parameters (e.g. `external-data-sources-db-schema`, `data-warehouse-source-setup({source_type, payload, prefix})`), a complete copy-paste JSON payload, and concrete error-recovery steps (show 400 message verbatim, manual webhook registration) covering the common cases. | 5 / 5 |
Workflow Clarity | A clearly sequenced Steps 1–7 workflow plus explicit validation checkpoints (db-schema validates creds before create, present table list and confirm prefix before creating, webhook-info-retrieve verification) and feedback loops for error recovery; validation is present so the batch/destructive cap does not apply. | 5 / 5 |
Progressive Disclosure | Sections are well organized and the sync-type guide is clearly signaled via a named markdown link, but the only bundle reference `./references/sync-types.md` points to a file that does not exist (no references/ directory), leaving a broken navigation target and the detailed sync-type rules only partially inlined. | 3 / 5 |
Total | 16 / 20 Passed |