terraform-aws
Patterns and best practices for AWS infrastructure as code with Terraform. Use when the user asks about Terraform module structure, naming conventions, state management, IAM policies (least privilege, OIDC), CI/CD pipelines for infrastructure (GitHub Actions, OIDC authentication), security scanning (Checkov, CKV_AWS checks), secrets management, KMS key policies, confused deputy prevention, Lambda function URL auth, API Gateway WAF/logging, or general IaC architecture decisions. Triggers on: Terraform, OpenTofu, IaC, modules, tfstate, remote state, OIDC, IAM, least privilege, GitHub Actions, CI/CD, infrastructure pipeline, AWS provider, Checkov, static analysis, IaC scanning, confused deputy, source ARN, KMS, CMK, secrets in state, ephemeral resources, Lambda function URL, API Gateway WAF.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers what the skill does (AWS Terraform patterns and best practices) and when to use it with comprehensive trigger terms. The description is specific, uses third-person voice correctly, and provides enough detail to distinguish it from generic IaC or AWS skills. The explicit 'Triggers on:' section is particularly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and domains: 'module structure, naming conventions, state management, IAM policies (least privilege, OIDC), CI/CD pipelines, security scanning (Checkov, CKV_AWS checks), secrets management, KMS key policies, confused deputy prevention, Lambda function URL auth, API Gateway WAF/logging'. | 3 / 3 |
Completeness | Clearly answers both 'what' (patterns and best practices for AWS infrastructure as code) and 'when' with explicit 'Use when...' clause listing specific scenarios, plus a comprehensive 'Triggers on:' section with explicit trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including both common terms ('Terraform', 'IAM', 'CI/CD', 'GitHub Actions') and specific technical terms users searching for help would use ('tfstate', 'remote state', 'confused deputy', 'Checkov', 'CKV_AWS'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: AWS + Terraform + specific security patterns. The combination of AWS-specific concerns (IAM, KMS, Lambda, API Gateway) with Terraform/IaC tooling creates a unique, non-conflicting scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates best practices across all dimensions. It serves as a highly efficient index to detailed reference materials while providing immediately actionable anti-patterns and decision frameworks. The reference loading strategy with line counts shows thoughtful consideration for token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, bullet points for anti-patterns, and avoids explaining concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete, specific guidance throughout: exact Checkov check IDs (CKV_AWS_28, CKV_AWS_119, etc.), specific IAM actions needed (sqs:ReceiveMessage, sqs:DeleteMessage, sqs:GetQueueAttributes), complete MCP server configuration JSON, and clear decision frameworks with specific criteria. | 3 / 3 |
Workflow Clarity | Clear reference loading strategy with explicit file-to-topic mapping. Decision frameworks provide unambiguous criteria for when to create modules. Anti-patterns section explicitly states what NOT to do with consequences, serving as implicit validation checkpoints. | 3 / 3 |
Progressive Disclosure | Excellent structure with SKILL.md as a concise overview pointing to three well-organized reference files. One-level-deep references with clear signaling (file names, line counts, topic mapping). Content appropriately split between quick reference and detailed materials. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- a-pavithraa/aws-serverless-skill
- Commit
f296935
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.