Cloudformation Template Creator - Auto-activating skill for AWS Skills. Triggers on: cloudformation template creator, cloudformation template creator Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/cloudformation-template-creator/SKILL.mdQuality
Discovery
7%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 description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions, natural user keywords, and explicit 'Use when' scenarios. The redundant trigger terms and circular self-reference provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, validates, and deploys AWS CloudFormation templates. Generates YAML/JSON infrastructure-as-code definitions for EC2, S3, Lambda, and other AWS resources.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions CloudFormation, CFN, AWS templates, infrastructure as code, IaC, stack creation, or needs to define AWS resources declaratively.'
Remove the redundant trigger term and add variations users actually say: 'CFN template', 'AWS stack', 'infrastructure template', 'deploy AWS resources'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Cloudformation Template Creator' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, validating, deploying, or any specific CloudFormation operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a circular reference to the skill name. No explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cloudformation template creator' listed twice) and overly specific. Missing natural variations users would say like 'CFN', 'infrastructure as code', 'AWS template', 'stack', 'YAML template', or 'deploy infrastructure'. | 1 / 3 |
Distinctiveness Conflict Risk | The CloudFormation focus provides some distinctiveness from general AWS skills, but 'AWS Skills skill category' is vague and could overlap with other AWS-related skills. The lack of specific use cases makes conflict risk moderate. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder with no actual instructional value. It contains only generic descriptions of what the skill claims to do without any CloudFormation-specific guidance, code examples, template patterns, or actionable instructions. Claude would gain nothing from this content that it doesn't already know.
Suggestions
Add concrete CloudFormation template examples showing common patterns (e.g., EC2 instance, S3 bucket, Lambda function) with complete YAML/JSON code
Include a workflow for template creation: define parameters → resources → outputs → validate with `aws cloudformation validate-template` → deploy
Provide specific best practices for CloudFormation (intrinsic functions, cross-stack references, nested stacks, drift detection) rather than generic claims
Remove all boilerplate text about 'when to use' and 'example triggers' - replace with actual template snippets and AWS CLI commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual CloudFormation-specific information. | 1 / 3 |
Actionability | There is zero concrete guidance - no CloudFormation template examples, no YAML/JSON snippets, no specific resource definitions, no commands. The skill describes what it claims to do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Creating CloudFormation templates involves specific steps (defining resources, parameters, outputs, validation, deployment) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual learning. No references to detailed materials, no examples file, no template patterns documentation - just empty marketing-style text. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
e9f9c93
Table of Contents
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.