CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-cloudformation-task-ecs-deploy-gh

Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when 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. Supports 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.

64

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is giuseppe-trisciuoglio/developer-kit

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well structured with an executable Quick Start that includes genuine validation and feedback loops, and a clean one-level-deep reference bundle. Its main weaknesses are padding in the best-practices, troubleshooting, and constraints sections (largely knowledge Claude already has) and small gaps in the multi-environment and blue/green examples that keep them from being fully copy-paste ready.

Suggestions

Trim the Constraints and Warnings and Common Troubleshooting sections to the non-obvious specifics and move the rest into references/best-practices.md, which already covers troubleshooting — this would lift conciseness.

Fix the multi-environment example so matrix variables (env_account, region, ECR_REGISTRY) are actually defined in the matrix, and show or reference a minimal appspec.yml so the blue/green example is executable.

Either link the unreferenced examples.md and reference.md from the References section or fold their content into the named reference files so every bundle file is discoverable.

DimensionReasoningScore

Conciseness

The Quick Start and Examples are efficient, but several sections pad with knowledge Claude already has: 'Docker layer caching', 'Multi-stage builds to minimize image size', 'Fargate Spot for cost savings', and generic constraint facts like 'Workflow File Size: Cannot exceed 1 MB' and 'Artifact Retention: Default 90-day retention'. Mostly efficient with some unnecessary explanation that could be trimmed or moved to the best-practices reference.

3 / 5

Actionability

The Quick Start is a fully executable, copy-paste-ready GitHub Actions workflow with pinned action versions, and the blue/green example gives concrete aws deploy commands. Minor gaps: the multi-environment example references `${{ matrix.env_account }}` and `${{ matrix.region }}` that are not defined in the shown matrix, and appspec.yml is used but never shown.

4 / 5

Workflow Clarity

The 8-step Instructions sequence is clear, and the Quick Start includes real validation checkpoints with feedback: 'Validate task definition' checks the rendered image against expected and exits 1 on mismatch, plus 'wait-for-service-stability: true'. Not a 5 because the numbered Instructions are only step names with no commands or per-step verification, deferring all detail to references.

4 / 5

Progressive Disclosure

Good structure: the body is an overview plus quick start, with clearly signaled one-level-deep references ('See references/workflow-examples.md', 'See references/best-practices.md') at the end of each section, and all five referenced files exist with real content. Minor gaps: the body runs ~250 lines with generic constraints/troubleshooting lists that belong in references, and two bundle files (examples.md, reference.md) exist but are never linked, leaving navigation slightly incomplete.

4 / 5

Total

15

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description in third-person voice with a clear 'what' and an explicit, multi-trigger 'Use when' clause. The action list is concrete and comprehensive; only minor keyword synonyms (Fargate, workflow) and slight overlap with sibling AWS skills keep it from top marks on two dimensions.

DimensionReasoningScore

Specificity

The description lists many concrete, specific actions: 'deploy ECS tasks and services with GitHub Actions CI/CD', 'building Docker images, pushing to ECR, updating ECS task definitions', 'configuring AWS OIDC authentication', and 'blue/green deployments... ECR private repositories with image scanning'. Coverage is comprehensive across the pipeline stages; not a 4 because there are no meaningful gaps in the action inventory.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' via 'Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD' and the 'when' via a concrete 'Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services...' trigger clause listing six concrete triggers.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'ECS', 'GitHub Actions', 'CI/CD', 'Docker images', 'ECR', 'task definitions', 'CloudFormation', 'OIDC', 'blue/green'. A few natural terms users would say are missing (e.g., 'Fargate', 'GitHub Actions workflow', 'deploy container'), so it is not the comprehensive 5 that includes synonyms and extensions.

4 / 5

Distinctiveness Conflict Risk

The ECS + GitHub Actions + CloudFormation CI/CD combination is a distinct niche with low conflict risk, but the skill body lists sibling skills (aws-cloudformation-ecs, aws-cloudformation-lambda) covering adjacent ECS territory, so minor overlap risk remains rather than the minimal-conflict 5.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository

giuseppe-trisciuoglio/developer-kit

Path

plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-task-ecs-deploy-gh/SKILL.md

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.