aws-cloudformation-task-ecs-deploy-gh
Deploy ECS tasks and services with GitHub Actions CI/CD. Use for building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready container deployment pipelines. Automate ECS deployments with proper security (OIDC or IAM keys), multi-environment support, blue/green deployments, ECR private repositories with image scanning, and CloudFormation infrastructure updates.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-task-ecs-deploy-gh77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 a strong, detailed description with excellent specificity and trigger term coverage for AWS ECS deployment workflows. The main weakness is the lack of an explicit 'Use when...' clause that would help Claude know exactly when to select this skill over others. Converting 'Use for...' to 'Use when...' with user-facing trigger scenarios would improve completeness.
Suggestions
Add an explicit 'Use when...' clause with user-facing triggers, e.g., 'Use when the user asks about deploying containers to ECS, setting up GitHub Actions for AWS, or automating Docker deployments to AWS.'
Consider adding common user phrasings like 'deploy to AWS', 'container CI/CD', or 'automate ECS' to capture more natural language queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'building Docker images', 'pushing to ECR', 'updating ECS task definitions', 'deploying ECS services', 'integrating with CloudFormation stacks', 'configuring AWS OIDC authentication', 'blue/green deployments', 'ECR private repositories with image scanning'. | 3 / 3 |
Completeness | Strong on 'what' with detailed capabilities, but lacks an explicit 'Use when...' clause. The 'Use for...' phrase partially addresses when to use it, but doesn't provide clear trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ECS', 'GitHub Actions', 'CI/CD', 'Docker images', 'ECR', 'task definitions', 'CloudFormation', 'OIDC', 'container deployment', 'blue/green deployments', 'IAM keys', 'multi-environment'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining ECS + GitHub Actions + CI/CD deployment. The combination of AWS ECS, ECR, CloudFormation, and GitHub Actions OIDC creates a distinct trigger profile unlikely to conflict with generic Docker or CI/CD skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable skill with excellent code examples and good progressive disclosure. The main weaknesses are verbosity in explanatory sections (Key Concepts, When to Use) that explain things Claude already knows, and missing explicit validation/verification steps in the deployment workflows. The troubleshooting section would be more valuable integrated as checkpoints within workflows.
Suggestions
Remove or significantly trim the 'Key Concepts' section - Claude already knows what GitHub Actions, ECR, ECS, and CloudFormation are
Remove the 'When to Use' section with trigger phrases - this adds ~30 lines without actionable value
Add explicit validation steps to workflows, e.g., after deployment: 'Verify deployment: aws ecs describe-services --cluster my-cluster --services my-service --query services[0].deployments'
Integrate key troubleshooting checks as validation steps within the workflow rather than as a separate reactive section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary sections like 'Key Concepts' that explain things Claude already knows (what GitHub Actions, ECR, ECS are). The 'When to Use' section with trigger phrases adds bulk without value. However, the code examples themselves are efficient. | 2 / 3 |
Actionability | Excellent actionability with fully executable YAML workflows, complete CloudFormation templates, and copy-paste ready code. The task-definition.json, appspec.yaml, and all GitHub Actions steps are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | While the deployment steps are listed clearly, there are no explicit validation checkpoints or feedback loops. For example, after 'Deploy to ECS' there's no verification step to confirm the deployment succeeded beyond 'wait-for-service-stability'. The troubleshooting section is reactive rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections progressing from Quick Start to advanced topics. References to external files (reference.md, examples.md) are well-signaled and one level deep. Content is appropriately organized with logical groupings. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (696 lines); consider splitting into references/ and linking | Warning |
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 |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.