cloudformation-template-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cloudformation-template-creatorCloudformation Template Creator - Auto-activating skill for AWS Skills. Triggers on: cloudformation template creator, cloudformation template creator Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing useful trigger guidance. It lacks any concrete actions, has redundant and limited trigger terms, and provides no 'Use when...' clause. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, validates, and modifies AWS CloudFormation templates. Generates YAML/JSON infrastructure-as-code definitions for AWS resources.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks about CloudFormation, CFN templates, AWS infrastructure as code, stack definitions, or needs to create/edit .yaml/.json AWS templates.'
Remove the duplicate trigger term and expand to include variations users naturally say: 'CloudFormation', 'CFN', 'AWS template', 'infrastructure template', 'stack template'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Cloudformation Template Creator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating, validating, modifying templates, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 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 'CloudFormation', 'CFN', 'infrastructure as code', 'AWS template', 'stack template', or 'YAML/JSON template'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'CloudFormation' is a specific AWS service, the lack of detail about what actions it performs could cause overlap with other AWS-related skills. The mention of 'AWS Skills skill category' suggests potential conflicts within that category. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 (e.g., using !Ref, !GetAtt, intrinsic functions, nested stacks, change sets)
Remove all generic boilerplate text and replace with actionable, CloudFormation-specific instructions
| 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
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.