Content
31%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 reads as a padded persona catalog of well-known cloud services rather than actionable, token-efficient guidance, and its only external reference is broken. It needs concrete procedures/examples and a real reference file to score higher.
Suggestions
Replace the service catalog and redundant persona sections (Behavioral Traits, Knowledge Base, Purpose) with a few concrete, executable workflows (e.g., a Terraform module skeleton, a cost-estimation command, a Well-Architected review checklist).
Add explicit validation checkpoints to the workflow (e.g., 'run `terraform validate` + `tfsec` before apply; confirm cost estimate against budget') with a fix-and-retry loop for destructive/batch infra changes.
Create the referenced `resources/implementation-playbook.md` (or remove the pointer) and move the bulk capability catalogs into clearly signaled one-level-deep reference files instead of inlining them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably verbose: it catalogs services Claude already knows (EC2, Lambda, EKS, RDS, S3, etc.) and restates the same material across redundant sections (Purpose, Capabilities, Knowledge Base, Behavioral Traits), adding little new information. | 2 / 5 |
Actionability | Guidance is high-level and abstract — 'Clarify goals ... Apply relevant best practices and validate outcomes' — with no executable code, commands, or specific steps, only describing what the persona does rather than instructing how. | 2 / 5 |
Workflow Clarity | An 8-step 'Response Approach' gives a rough sequence, but it lacks validation checkpoints or error-recovery feedback loops, and the only validation mention ('validate outcomes') is implicit and vague. | 3 / 5 |
Progressive Disclosure | The single reference to `resources/implementation-playbook.md` points at a file that does not exist (no resources/references/scripts/assets directories present), and the large capability catalogs that belong in separate files are inlined. | 2 / 5 |
Total | 9 / 20 Passed |