cloudformation-template-creator
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 extremely weak — it is essentially just the skill name repeated with no substantive content about capabilities, use cases, or trigger scenarios. It provides no actionable information for Claude to determine when to select this skill over others, and the duplicate trigger term adds no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates AWS CloudFormation templates in YAML/JSON, defines resource configurations, sets up stack parameters, outputs, and mappings.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create CloudFormation templates, define AWS infrastructure as code, set up CFN stacks, or generate .yaml/.json resource definitions.'
Differentiate from other AWS skills by specifying the unique scope, e.g., 'Focuses specifically on CloudFormation template authoring, not CDK, SAM, or Terraform.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Cloudformation Template Creator') but does not describe any concrete actions like 'generates CloudFormation YAML/JSON templates, defines AWS resources, configures stack parameters.' It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and there is no 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cloudformation template creator' repeated twice. It misses natural user phrases like 'CloudFormation stack', 'AWS infrastructure as code', 'CFN template', 'deploy AWS resources', '.yaml template', or 'IaC'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Cloudformation' and 'AWS' provides some domain specificity that distinguishes it from generic skills, but the lack of detail about what it specifically does (vs. other AWS skills like CDK or SAM) creates overlap risk within the AWS Skills category. | 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 is an empty placeholder with no actionable content. It consists entirely of generic boilerplate that could apply to any topic—simply substituting 'cloudformation template creator' into a template. It provides zero value for guiding Claude in creating CloudFormation templates.
Suggestions
Add concrete, executable CloudFormation template examples (e.g., a minimal YAML template for an S3 bucket, an EC2 instance, or a Lambda function) that Claude can use as starting points.
Define a clear workflow: gather requirements → select resources → write template → validate with `aws cloudformation validate-template` → deploy with `aws cloudformation deploy` → verify stack status.
Include CloudFormation-specific best practices such as parameterization, output exports, cross-stack references, intrinsic function usage, and common pitfalls (circular dependencies, resource limits).
Remove all generic boilerplate ('This skill provides automated assistance...', 'Example Triggers', etc.) and replace with lean, actionable content that assumes Claude's existing knowledge of AWS.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'cloudformation template creator' excessively, and contains zero substantive information about actually creating CloudFormation templates. | 1 / 3 |
Actionability | There are no concrete instructions, no code examples, no CloudFormation template snippets, no specific commands, and no executable guidance whatsoever. The skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all—no steps for creating a CloudFormation template, no validation checkpoints, no sequencing of any kind. The 'Capabilities' section vaguely mentions validation but provides no actual process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 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 | |
- Commit
3a2d27d
- 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.