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.

1.16x

Quality

82%

Does it follow best practices?

Impact

97%

1.16x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference with executable code throughout, held back by missing validation checkpoints around destructive stack operations and a monolithic structure that inlines content better split across files.

Suggestions

Insert a `validate-template` checkpoint before `create-stack`/`update-stack` and add an explicit confirm/verify step before `delete-stack` to satisfy the destructive-operation validation requirement.

Move the full CLI reference tables and complete resource templates (VPC, DynamoDB) into separate reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim the introductory marketing sentence and consolidate generic best-practice bullets to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly lean and efficient — terse concept definitions and complete code examples with little padding — though the intro marketing line ('Define infrastructure as code, version control it, and deploy consistently across environments') and a few generic best-practice bullets could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready YAML templates and CLI commands with full flags cover common cases (deploy, change sets, Lambda, VPC, DynamoDB, troubleshooting).	5 / 5
Workflow Clarity	Multi-step sequences exist (create-stack → wait; create → describe → execute change set) but destructive operations (delete-stack, update-stack) lack validation checkpoints, and validate-template is not integrated into the deploy workflow — capping this at 3 per the destructive-operation guidance.	3 / 5
Progressive Disclosure	Has a table of contents and clear section headers, but at ~380 lines the bulk CLI reference tables and full resource templates are inlined rather than split into separate reference files; no bundle files are provided.	3 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both the skill's purpose and concrete trigger conditions with minimal conflict risk. Only slightly limited by a few missing natural synonyms in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ('AWS CloudFormation infrastructure as code for stack management') and when ('Use when writing templates, deploying stacks...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('templates', 'deploying stacks', 'drift', 'nested stacks') but is missing some common synonyms/variations like 'CloudFormation template', 'stack update', or '.yaml/.json template'.	4 / 5
Distinctiveness Conflict Risk	Names AWS CloudFormation explicitly with a clear niche and distinct triggers, making overlap with other IaC skills (Terraform, CDK) minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: itsmostafa/aws-agent-skills
Path: skills/cloudformation/SKILL.md
Commit: e786d25

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.