CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudformation-best-practices

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

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cloudformation-best-practices/SKILL.md

The canonical home for this skill is cloudformation-best-practices in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, well-structured CloudFormation reference with executable examples and concrete troubleshooting guidance. Its main weakness is workflow clarity: it presents practices as a flat checklist rather than a sequenced, validated deployment/review workflow.

Suggestions

Reframe the Instructions as an ordered deployment/review workflow with explicit validation checkpoints (e.g., '1. Validate with aws cloudformation validate-template; 2. Only if valid, deploy; 3. On failure, run continue-update-rollback and fix root cause').

Add a brief feedback loop for stack failures (validate -> diagnose drift -> rollback -> redeploy) to satisfy the destructive-operation cap.

Remove the 'You are an expert in AWS CloudFormation...' preamble to tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's familiarity with CloudFormation basics, with only minor padding such as the 'You are an expert in AWS CloudFormation...' role preamble that could be trimmed.

4 / 5

Actionability

Provides concrete directives (DeletionPolicy: Retain, !Sub over !Join), a complete executable VPC template, and specific CLI commands (aws cloudformation validate-template, continue-update-rollback --resources-to-skip), with only limited example coverage beyond one template.

4 / 5

Workflow Clarity

The Instructions are a best-practice checklist rather than a checkpointed sequence, and while a validation step is present as a bullet, CloudFormation deployment is destructive enough that a missing explicit validate-then-proceed feedback loop caps the score at 3.

3 / 5

Progressive Disclosure

A single self-contained file organized into clearly labeled sections (Use when, Do not use, Instructions, Examples, Best Practices, Troubleshooting) with no need for external references, though slightly over the 50-line simple-skill threshold.

4 / 5

Total

15

/

20

Passed

Description

78%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 concise, third-person description that pairs a concrete capability list with an explicit 'Use when' trigger and a well-scoped niche. It would reach the top tier by broadening the trigger clause with more natural phrases (e.g., 'stack failures', 'drift', '.yaml/.json templates').

Suggestions

Expand the 'Use when' clause with additional natural triggers users actually say, such as 'stack creation/update failures', 'template drift', or '.yaml/.json CloudFormation files'.

Replace 'production-ready patterns' with a more concrete capability to lift specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('template optimization, nested stacks, drift detection, and production-ready patterns'), with only minor gaps such as 'production-ready patterns' being somewhat generic.

4 / 5

Completeness

Clearly answers both 'what' (optimization, nested stacks, drift detection, patterns) and 'when' ('Use when writing or reviewing CF templates'), though the trigger clause is a single narrow condition rather than multiple concrete triggers.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('writing or reviewing CF templates', 'CloudFormation') plus the 'CF' synonym, but omits file extensions (.yaml/.json) and some common variations.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear CloudFormation-specific niche with distinct, domain-locked triggers, presenting minimal overlap risk with unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.