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.
An exceptionally actionable, dense troubleshooting reference with well-sequenced diagnostic workflows, explicit verification steps, and hard-won Foundry-specific gotchas on every line. Its weaknesses are token duplication between the Quick Diagnosis tree and the Common Issue Patterns table, and the absence of any progressive disclosure — all detail lives inline in a single ~370-line file.
Suggestions
Split deep-dive material that isn't needed at triage time into one-level-deep reference files (e.g. references/identity-and-scopes.md for the identity table and 403-rule exceptions, references/sandbox-connection-issue.md for the token-cache essay) and signal them from the relevant sections, keeping SKILL.md as the diagnosis tree plus core procedures.
Deduplicate the Common Issue Patterns table against the Quick Diagnosis tree: keep each symptom in exactly one place (tree for interactive diagnosis, table only for symptoms not already covered) and cross-link instead of restating fixes.
Consider moving the Visual Debugging with Screenshots and Debugging App Install Failures walkthroughs into a reference file, leaving one-line pointers in the main body to shorten the always-loaded context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every line is Foundry-specific knowledge Claude cannot already know, with no general-concept padding, but the Common Issue Patterns table substantially duplicates the Quick Diagnosis tree (deploy hangs, login hangs, 403, connection issue, CI auth), so minor trimming is possible. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout — `foundry functions logs <exec_id> --refresh`, `foundry apps deploy --change-type Patch --change-log "fix handler error" --no-prompt`, complete env-var and profile-create blocks, and a concrete version-pin fix (`--version v0.0.4-pre-release`) — with specific examples covering the common failure cases. | 5 / 5 |
Workflow Clarity | The Function Runtime Debugging workflow is sequenced Step 1–5 with explicit verification (re-execute after redeploy), destructive recovery paths carry validation ("Validate with test deployment", backup + incremental re-deploy), and the Pre-Escalation Checklist plus log-retrieval fallback loops close the feedback loop. | 5 / 5 |
Progressive Disclosure | No bundle files exist and all ~370 lines are inline: deep-dive material ("Which Identity Makes the Call", the sandboxed connection-issue essay, Visual Debugging, Manifest Issues recovery) sits in SKILL.md where a one-level-deep reference file would be appropriate, fitting 'some structure but content that should be separate is inline'. | 3 / 5 |
Total | 17 / 20 Passed |