Content
75%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.
A strong, highly actionable skill body with precise commands, signatures, and error-recovery loops, well-structured around a routing table to a rich bundle. Its main weakness is length: a large inline 'must-surface facts' block and some cross-section constraint repetition dilute conciseness and keep progressive disclosure from a top score.
Suggestions
Move the eight numbered 'RDS-managed facts the agent must always surface' lists into a dedicated reference (e.g. references/rds-managed-facts.md) and keep only a short pointer plus the one or two highest-frequency facts inline, to improve both conciseness and progressive disclosure.
Consolidate the repeated credential-handling constraint ('MUST NOT prompt the user to paste credentials') into a single stated rule in Verify Dependencies and reference it from Execute Workflow and Security Considerations instead of restating it verbatim.
Tighten the Execute Workflow phase into an explicit numbered sequence with validation checkpoints (collect params → validate formats → run command → poll task status) so the workflow matches the precision of the routing and troubleshooting sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is high-signal and RDS-Db2-specific rather than padded with concepts Claude knows, but the ~80-line inline 'RDS-managed facts the agent must always surface' block and repeated credential-handling constraints across sections add length that could be tightened or offloaded to references. | 3 / 5 |
Actionability | Fully executable guidance throughout: exact AWS CLI commands ('aws rds create-db-instance-read-replica --replica-mode mounted …'), precise rdsadmin signatures ('rdsadmin.restore_database(dbname, type, prefix, bucket, region)'), concrete tag syntax, and an error→cause→fix troubleshooting table. | 5 / 5 |
Workflow Clarity | Clear three-phase sequence (Verify Dependencies → Classify and Route → Execute Workflow) with an explicit dependency-validation gate and troubleshooting feedback loops; the Execute Workflow phase reads as guidance rather than a crisp numbered sequence with checkpoints, keeping it just below the top anchor. | 4 / 5 |
Progressive Disclosure | Excellent routing table maps user phrases to 15 real one-level-deep references plus 8 scripts and assets (all verified to exist), but the large inline mandatory-facts section is detailed content that arguably belongs in a reference, a minor organization gap. | 4 / 5 |
Total | 16 / 20 Passed |