Content
50%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized but monolithic reference document heavy on tables and lists, light on actionable detail. It lacks executable guidance, validation checkpoints, and progressive disclosure into bundle files.
Suggestions
Move the large service-comparison and cost tables into bundled reference files (e.g. references/service-matrix.md) and keep SKILL.md as a decision-oriented overview.
Replace vague strategy bullets with concrete, executable guidance (e.g. specific cost-analysis commands or a worked decision example).
Add explicit validation checkpoints to the migration phases (e.g. 'verify workload parity before cutover', rollback triggers on failure).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly compact tables and lists, but it is a long monolithic reference dump (~180 lines) with some generic filler ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that could be trimmed or split out. | 2 / 3 |
Actionability | It catalogs services, patterns, and strategies but gives no executable commands or concrete code; items like 'Right-size resources', 'Implement comprehensive monitoring', and 'Optimize data transfer costs' describe rather than instruct. | 2 / 3 |
Workflow Clarity | The migration strategy offers a four-phase sequence, but there are no explicit validation checkpoints or feedback loops for these risky batch/destructive operations, capping clarity at 2. | 2 / 3 |
Progressive Disclosure | Everything lives in one file with no bundle references to offload detailed tables; only 'Related Skills' links outward. It is organized into sections but the reference material should be split into separate files. | 2 / 3 |
Total | 8 / 12 Passed |