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.
A highly actionable, well-sequenced skill body anchored in concrete snyk/Terraform commands, with clear phases and useful error-handling guidance. Its main weaknesses are the lack of an explicit validation checkpoint before destructive remediation and broken/missing file references that undermine progressive disclosure.
Suggestions
Add an explicit validation gate before destructive remediation in Phase 4.2 — e.g., confirm the resource is not referenced in Terraform state/configuration and prompt for user confirmation before running 'aws s3 rb --force' or 'aws ec2 terminate-instances'.
Either create the referenced SERVICES.md and EXAMPLES.md files, or remove/replace the broken 'see SERVICES.md' and 'see EXAMPLES.md' links with pointers to the existing references/drift-remediation.md.
Link the existing references/drift-remediation.md from the Phase 4 Remediation section so the bundled reference is actually discoverable, and consider moving the worked examples and service-coverage tables out of SKILL.md into those reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean — code blocks, command snippets, and tables carry the content with no over-explanation of Terraform or drift concepts — but small trims remain ('Core Principle: Your cloud should match your code' and the illustrative 'Scan Date: 2024-01-15' in the report template). | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout — 'snyk iac describe --from=tfstate://terraform.tfstate', 'aws sts get-caller-identity', 'terraform import aws_s3_bucket.manual_bucket prod-logs-manual' — covering scan, remote-state, service-specific, JSON-output, and remediation cases. | 5 / 5 |
Workflow Clarity | A clear five-phase sequence (Setup → Run → Analyze → Remediation → Prevention) with Phase 1 setup validation, but Phase 4.2 destructive operations ('aws s3 rb --force', 'aws ec2 terminate-instances') are guarded only by a vague 'After verification' rather than an explicit validation gate, capping destructive-op workflows at 3. | 3 / 5 |
Progressive Disclosure | Section/phase structure exists and references are signaled ('see SERVICES.md', 'see EXAMPLES.md'), but both referenced files are absent from the bundle while the one present reference (drift-remediation.md) is never linked from the body, and ~340 lines of content are largely inlined. | 3 / 5 |
Total | 15 / 20 Passed |