cloudformation-best-practices

CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudformation-best-practices/SKILL.md

Quality

Content

68%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 solid CloudFormation skill that provides actionable guidance with a good concrete example and useful best practices. Its main weakness is the lack of an explicit deployment workflow with validation checkpoints, and it doesn't fully cover all topics mentioned in its description (nested stacks, drift detection). The content is well-structured and reasonably concise.

Suggestions

Add an explicit deployment workflow with validation feedback loop: validate -> fix -> deploy -> verify (e.g., check stack events for failures)

Add content or examples covering nested stacks and drift detection, which are mentioned in the skill description but absent from the body

Dimension	Reasoning	Score
Conciseness	Generally efficient with minimal over-explanation. The 'Use this skill when' and 'Do not use this skill when' sections add some overhead but are brief. The instructions are terse and assume Claude's competence with AWS concepts.	4 / 5
Actionability	Provides a concrete, executable YAML template example and specific CLI commands (validate-template, continue-update-rollback). However, some instructions remain at the guideline level (e.g., 'use Conditions to support multi-environment templates') without showing the full pattern in action.	4 / 5
Workflow Clarity	The instructions list steps but lack a clear sequential workflow with validation checkpoints. There's no explicit feedback loop for template validation failures (validate -> fix -> re-validate -> deploy). The troubleshooting section helps but doesn't integrate into a deployment workflow.	3 / 5
Progressive Disclosure	Content is well-organized with clear sections (Instructions, Examples, Best Practices, Troubleshooting). For a standalone skill with no bundle files, the structure is appropriate and navigable. Could benefit from references to separate files for nested stack patterns or drift detection details mentioned in the description.	4 / 5
	Total	15 / 20 Passed

Description

67%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.

This is a solid description that clearly identifies the CloudFormation domain and lists several specific capabilities. The 'Use when' clause is present but could benefit from broader trigger terms including common synonyms and related AWS terminology. The description is concise and uses proper third-person voice.

Suggestions

Add more natural trigger terms and synonyms such as 'AWS', 'CFN', 'infrastructure as code', 'IaC', 'stack deployment', or '.yaml/.json templates' to improve discoverability.

Expand the 'Use when' clause with additional trigger scenarios like 'troubleshooting stack errors', 'converting infrastructure to code', or 'managing AWS resources via templates'.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: 'template optimization', 'nested stacks', 'drift detection', and 'production-ready patterns'. These are concrete CloudFormation concepts, though coverage could be more comprehensive (e.g., mentioning resource definitions, parameter handling, outputs, mappings).	4 / 5
Completeness	Has a clear 'what' (optimization, nested stacks, drift detection, production-ready patterns) and an explicit 'when' ('Use when writing or reviewing CF templates'). The 'when' clause is present but could be more specific with additional trigger scenarios like troubleshooting stack failures or converting manual resources to CF.	4 / 5
Trigger Term Quality	Includes 'CloudFormation', 'CF templates', 'nested stacks', and 'drift detection' which are relevant keywords. However, it misses natural user terms like 'AWS', 'infrastructure as code', 'IaC', '.yaml', '.json', 'stack', 'CFN', or 'deploy infrastructure'.	3 / 5
Distinctiveness Conflict Risk	CloudFormation is a specific AWS service, making this fairly distinct from general IaC or Terraform skills. However, 'template optimization' and 'production-ready patterns' are somewhat generic phrases that could overlap with other AWS or IaC skills. The abbreviation 'CF' could also be ambiguous.	4 / 5
	Total	15 / 20 Passed

Validation

90%

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 — 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/cloudformation-best-practices/SKILL.md
Commit: 57c135b

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.