Content
72%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 — exact AWS CLI commands, an allow-listed set of config keys, concrete file paths, and complete templates for all five modes — and largely token-efficient. The switch mode's batch patching of MCP config files lacks a post-write validation/feedback loop (capping workflow clarity), and every section's pointer to references/aws-mcp-profiles.md is a dangling reference since the file is not in the bundle.
Suggestions
Add a validate-after-patch step to the switch mode (e.g., re-parse each patched mcp.json/settings.json to confirm it is still valid JSON, and offer to fix and re-verify on failure) to create a real feedback loop for the batch config modification.
Ship references/aws-mcp-profiles.md in the bundle (or remove the six "Reference:" pointers) so the one-level-deep navigation actually resolves.
State the credential-boundary and TTL-"unknown" rules once in the Credential boundary section and reference them briefly from each mode, instead of repeating the full sentences across discover, status, login, and org-scan.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is operational throughout — exact commands, an allow-listed set of config keys, concrete file paths — with no explanations of concepts Claude already knows. Minor redundancy could be trimmed: the TTL-"unknown" caveat ("Do not read credential caches" / "never inspect a credential cache" / "Report TTL as unknown unless the user shared an expiration timestamp") is repeated across four sections, and "Reference: references/aws-mcp-profiles.md → ..." lines appear six times. Fits the 4 anchor (efficient, minor instances that could be trimmed) rather than 5. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready guidance: `aws configure list-profiles`, `aws configure get <key> --profile <profile>` with an enumerated key allow-list, `aws sts get-caller-identity --profile <profile>`, `aws organizations list-accounts --profile <mgmt-profile> --output json`, exact config paths (~/.vscode/mcp.json, ~/.claude/settings.json, .vscode/mcp.json), plus complete ini and YAML templates. Specific examples cover the common cases for every mode. | 5 / 5 |
Workflow Clarity | Sequences are numbered and several modes have real checkpoints (login validates with `aws sts get-caller-identity` then auto-runs status; switch halts without --confirm on prod and shows a patched-entries diff). However, the switch mode batch-modifies multiple MCP config files with no post-write validation step (e.g., re-parsing the patched JSON to confirm validity) and no validate→fix→retry feedback loop, so the rubric's cap for batch/destructive operations without validation applies, holding this at 3 despite otherwise 4-5 quality sequencing. | 3 / 5 |
Progressive Disclosure | Mode sections are well structured and every external pointer is clearly signaled one level deep with named sections ("references/aws-mcp-profiles.md → Profile Type Detection, Credential Lifecycle"), but that referenced file is absent from the bundle (no references/ directory exists), leaving all six pointers dangling. At ~310 lines, the body also inlines full ini/YAML templates and sample outputs that could partly live in the reference. Fits 3 (references present but navigation does not resolve against the actual bundle) rather than 4. | 3 / 5 |
Total | 15 / 20 Passed |