cloudformation
AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.
92
89%
Does it follow best practices?
Impact
97%
1.16xAverage score across 3 eval scenarios
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 a well-crafted skill description that follows best practices. It uses third person voice, clearly states the domain (AWS CloudFormation), lists specific capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive enough to distinguish it from other infrastructure or AWS-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'writing templates, deploying stacks, managing drift, troubleshooting deployments, organizing infrastructure with nested stacks' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('AWS CloudFormation infrastructure as code for stack management') and when ('Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'CloudFormation', 'templates', 'stacks', 'drift', 'deployments', 'nested stacks', 'infrastructure as code' - good coverage of domain-specific terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to AWS CloudFormation with distinct triggers like 'CloudFormation', 'stacks', 'drift', 'nested stacks' - unlikely to conflict with other infrastructure tools like Terraform or general AWS skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted CloudFormation skill with excellent actionability and conciseness. The code examples are complete and executable, covering common infrastructure patterns effectively. The main weaknesses are the lack of explicit validation checkpoints in workflows and the monolithic structure that could benefit from splitting detailed patterns into separate reference files.
Suggestions
Add explicit validation steps to the deployment workflow, e.g., 'Validate template before deploying: aws cloudformation validate-template --template-body file://template.yaml'
Consider splitting detailed resource patterns (VPC, Lambda, DynamoDB) into a separate PATTERNS.md file, keeping only the basic template structure in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing direct code examples and commands without explaining basic concepts Claude already knows. No unnecessary padding or verbose explanations of what CloudFormation is or how AWS works. | 3 / 3 |
Actionability | Fully executable YAML templates and bash commands throughout. All examples are copy-paste ready with complete, working code for common patterns like Lambda functions, VPCs, and DynamoDB tables. | 3 / 3 |
Workflow Clarity | Steps are listed for stack operations and change sets, but validation checkpoints are implicit. The troubleshooting section helps with error recovery, but the main workflows lack explicit 'validate before proceeding' steps for destructive operations like stack updates. | 2 / 3 |
Progressive Disclosure | Good internal organization with table of contents and clear sections, but the document is quite long (~300 lines) with detailed examples inline. Some content like the VPC and DynamoDB patterns could be split into separate reference files with links from the main skill. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- itsmostafa/aws-agent-skills
- Commit
5df6da7
- 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.