aws-cloudformation-ecs
AWS CloudFormation patterns for ECS clusters, services, and task definitions. Use when creating ECS infrastructure with CloudFormation, configuring container definitions, scaling policies, service discovery, load balancing integration, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references, and blue/green deployments with CodeDeploy.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-ecs90
Does it follow best practices?
Validation for skill structure
Discovery
100%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 an excellent skill description that clearly defines its scope (CloudFormation for ECS), lists comprehensive specific capabilities, and includes explicit 'Use when' guidance with abundant natural trigger terms. The description is appropriately detailed without being verbose, uses correct third-person voice, and carves out a distinct niche that would be easily distinguishable from other AWS or infrastructure skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'ECS clusters, services, and task definitions', 'container definitions, scaling policies, service discovery, load balancing integration', and template structure elements like 'Parameters, Outputs, Mappings, Conditions, cross-stack references, and blue/green deployments with CodeDeploy'. | 3 / 3 |
Completeness | Clearly answers both what ('AWS CloudFormation patterns for ECS clusters, services, and task definitions') and when ('Use when creating ECS infrastructure with CloudFormation, configuring container definitions, scaling policies...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'AWS', 'CloudFormation', 'ECS', 'clusters', 'services', 'task definitions', 'container definitions', 'scaling policies', 'service discovery', 'load balancing', 'Parameters', 'Outputs', 'Mappings', 'Conditions', 'cross-stack references', 'blue/green deployments', 'CodeDeploy'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining AWS CloudFormation with ECS specifically, plus detailed sub-features like CodeDeploy blue/green deployments. Unlikely to conflict with general AWS skills or generic CloudFormation skills due to the ECS focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive skill for AWS CloudFormation ECS patterns. It excels in actionability with complete, executable templates and clear workflow documentation for complex operations like blue/green deployments. The main weakness is some verbosity that could be trimmed, particularly in introductory sections and explanatory comments within templates.
Suggestions
Remove or condense the 'When to Use' section as it largely duplicates the skill description and adds little value for Claude
Reduce inline comments in YAML templates that explain obvious AWS concepts (e.g., 'Security group for ALB' is self-evident from the resource name)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the 'When to Use' section that largely repeats the description, and some explanatory comments that Claude would already understand. The template examples are thorough but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable CloudFormation YAML templates with complete resource definitions, CLI commands for stack operations, and copy-paste ready code. Examples include all necessary properties and are production-ready. | 3 / 3 |
Workflow Clarity | Multi-step processes like change sets and blue/green deployments are clearly sequenced with numbered steps. The change set workflow explicitly includes validation (review changes) before execution, and drift detection includes clear status values and remediation paths. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section headers, appropriate use of inline examples for common patterns, and explicit references to REFERENCE.md and EXAMPLES.md for detailed information. Content is appropriately split between overview and detailed sections. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1440 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | 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.