ecs-deployment

ECS deployment strategies including rolling updates, blue-green with CodeDeploy, canary releases, and GitOps workflows. Covers deployment circuit breakers, rollback strategies, and production deployment patterns. Use when deploying ECS services, implementing blue-green deployments, setting up CI/CD pipelines, or managing production releases.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ecs-deployment/SKILL.md

Quality

Content

57%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.

A thorough, largely executable reference covering rolling, blue-green, canary, GitOps, and rollback patterns with concrete code. It is held back by duplicated/inlined content that belongs in the reference, two broken reference links, an undefined-variable bug in the canary example, and missing validation feedback loops in the production deployment workflows.

Suggestions

Create the missing references/cicd-pipelines.md and references/deployment-monitoring.md (or remove their links) so the Progressive Disclosure section does not point at non-existent files.

Dedupe the blue-green Terraform: keep only a concise sketch in SKILL.md and move the full ~140-line CodeDeploy configuration into references/blue-green-setup.md.

Fix shift_traffic to pass stable_tg_arn and canary_tg_arn as parameters, and turn the canary 'Monitor metrics...' comments into an explicit validate-then-rollback checkpoint (check error-rate/latency, rollback on breach).

Dimension	Reasoning	Score
Conciseness	Mostly code-dense and assumes Claude's competence without explaining basic concepts, but the ~140-line blue-green Terraform block is duplicated verbatim in references/blue-green-setup.md, inlining content that belongs in the reference; not 4 because the duplication is more than a minor trim.	3 / 5
Actionability	Largely copy-paste-ready boto3, Terraform, YAML, and CLI examples cover the common deployment cases; not 5 because shift_traffic references undefined stable_tg_arn/canary_tg_arn, making that one example non-executable as written.	4 / 5
Workflow Clarity	Numbered steps and a wait_for_deployment monitor exist, but the canary flow uses 'Monitor metrics...' comments as implicit checkpoints with no validate-then-rollback feedback loop; the rubric caps risky/batch production-deployment workflows lacking validation at 3, so not 4.	3 / 5
Progressive Disclosure	Clear section structure and a dedicated references section, but 2 of 3 referenced files (cicd-pipelines.md, deployment-monitoring.md) do not exist and the blue-green Terraform that belongs in the reference is inlined/duplicated; not 4 because broken references and duplication exceed minor organization gaps.	3 / 5
	Total	13 / 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, specific description that clearly states what the skill covers and when to invoke it, with comprehensive strategy coverage and natural trigger phrases. The only weaknesses are a few missing synonyms and minor overlap risk from the broad CI/CD and production-release triggers.

Dimension	Reasoning	Score
Specificity	Names the ECS deployment domain and lists multiple concrete strategies — 'rolling updates, blue-green with CodeDeploy, canary releases, and GitOps workflows' plus 'deployment circuit breakers, rollback strategies' — giving comprehensive coverage; not 4 because no meaningful coverage gaps remain.	5 / 5
Completeness	Explicitly answers 'what' (the deployment strategies and patterns covered) and 'when' via a concrete 'Use when deploying ECS services, implementing blue-green deployments, setting up CI/CD pipelines, or managing production releases' clause; not 4 because both halves are explicit and specific.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ('deploying ECS services', 'blue-green deployments', 'setting up CI/CD pipelines', 'managing production releases'); not 5 because some natural synonyms/variants (Fargate, task definition, CodeDeploy as a standalone trigger) are absent.	4 / 5
Distinctiveness Conflict Risk	Clear ECS-deployment niche with distinct triggers; not 5 because 'CI/CD pipelines' and 'production releases' are broad enough to overlap with adjacent CI/CD or general ECS skills.	4 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (564 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 2 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/ecs-deployment/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.