Content
72%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 content is lean, well-structured, and largely actionable with concrete curl commands across AWS/GCP/Azure, but undefined helper functions and missing validation checkpoints for destructive credential operations keep it from full marks.
Suggestions
Define or remove the `metadata_endpoints()` helper and the `kg_add_node`/`kg_add_edge` functions, or link to the skill that defines them.
Add an explicit validation step after credential extraction (e.g. run `aws sts get-caller-identity` to confirm the creds work before promoting them).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's knowledge — no basic explanations of IMDS/SSRF — with lean tables and executable commands where every token earns its place. | 3 / 3 |
Actionability | Most commands are copy-paste ready curl/jq snippets, but the undefined `metadata_endpoints()` helper and the `kg_add_node`/`kg_add_edge` promotion functions are referenced without definition, leaving key pieces incomplete. | 2 / 3 |
Workflow Clarity | Numbered sections give a clear identify→extract→promote sequence, but credential extraction and knowledge-graph promotion are batch/destructive operations with no explicit validation checkpoint (e.g. verify creds before promoting), which caps the score at 2. | 2 / 3 |
Progressive Disclosure | Well-organized into clear numbered sections with one-level, clearly signaled references ('see SSRF skill catalog', 'Pivot to aws-iam-enum/SKILL.md'); no deep nesting or monolithic wall. | 3 / 3 |
Total | 10 / 12 Passed |