Content
85%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 and well-structured with a clear validated workflow and exemplary progressive disclosure to verified bundle files. Its only real weakness is moderate redundancy between the inline efficiency rules and the Common Pitfalls list, which inflates token usage without adding new information.
Suggestions
Consolidate the "Common Pitfalls" list so each warning appears once; cross-reference pitfalls from the inline workflow steps rather than restating them (e.g., the "NEVER use Read or sed on large spec files" warning and the "Don't add x-cs-operation-config when not asked" guidance are both currently duplicated).
Trim repeated guidance about trusting the adapt script for auth conversion — it is stated in step 2, "Efficiency Rules", and "Common Pitfalls"; stating it once with a forward reference would save tokens.
The "Reading Guide" table duplicates the inline reference links already present in their sections; consider keeping only the inline links or only the table to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and high-signal, but several warnings are duplicated across "Efficiency Rules" and "Common Pitfalls" (e.g., "NEVER use Read or sed on large spec files" appears both inline and in pitfalls), and the "Don't add what wasn't asked for" guidance is repeated, so it could be tightened. | 3 / 5 |
Actionability | Provides fully executable, copy-paste-ready guidance throughout: the `foundry api-integrations create` command with flags, the adapt script invocation with full venv setup, the JavaScript Foundry-JS calling pattern, and a python3 snippet for patching specific operations. | 5 / 5 |
Workflow Clarity | A clearly numbered three-step sequence (Download, Adapt, Register) with explicit validation ("Validate immediately after registering `foundry apps validate --no-prompt`") and a `--dry-run` feedback loop for the adapt step, plus explicit error-handling notes (the `--description`/EOF gotcha). | 5 / 5 |
Progressive Disclosure | A clear overview body with well-signaled, one-level-deep references — all three linked reference files (spec-adaptation-examples, auth-examples, calling-patterns) and the bundled script exist and are surfaced both inline and in a consolidated "Reading Guide" table, making navigation easy. | 5 / 5 |
Total | 18 / 20 Passed |