Name: ecs-fargate
Rating: 64 (1 reviews)
Author: fernandezbaptiste

ecs-fargate

AWS Fargate serverless container compute for ECS. Covers Fargate vs EC2 decision guide, CPU/memory sizing, platform versions, Fargate Spot cost optimization, Graviton/ARM architecture, networking, and EFS integration. Use when deploying serverless containers, optimizing Fargate costs, sizing Fargate tasks, or choosing between Fargate and EC2 launch types.

Quality

76%

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 ./.claude/skills/ecs-fargate/SKILL.md

The canonical home for this skill is ecs-fargate in fernandezbaptiste/Skrillz

Quality

Content

65%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 body is highly actionable with abundant executable code, but it is over-long for a SKILL.md and its progressive disclosure is broken: two of three referenced files are missing while their subject matter is inlined. Decision guidance is clear though it lacks explicit validation checkpoints.

Suggestions

Create references/networking.md and references/storage.md and move the inlined awsvpc/VPC-endpoint and EFS/ephemeral-storage sections into them, leaving concise summaries plus the links in SKILL.md — this fixes the broken references and reduces token load.

Trim the redundant "Best Practices" list and the "Progressive Disclosure: Quick Start" summary, both of which restate content already covered in the body.

For destructive or batch operations (e.g. platform-version changes, Spot cutover), add an explicit validate-then-proceed checkpoint sequence so workflow_clarity can exceed 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete tables and code, but the trailing "Best Practices" list and "Progressive Disclosure" summary restate points already covered, and per-section terraform+boto3 duplication inflates length, so it could be tightened rather than earning anchor 4.	3 / 5
Actionability	It provides extensive copy-paste-ready HCL, boto3, Dockerfile, and bash examples plus executable sizing and cost-estimation functions that cover the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Decision guidance (Fargate vs EC2, the sizing decision tree, Spot capacity-provider strategy) is clear, but there is no explicit multi-step sequence with validation checkpoints; the content is reference-oriented, so it sits at anchor 3 rather than 4.	3 / 5
Progressive Disclosure	Section structure and a signaled references block exist, but two of the three referenced files (networking.md, storage.md) do not exist in ./references/ and the networking/EFS/storage content that belongs in them is inlined in SKILL.md, matching the anchor-3 "content that should be separate is inline" pattern.	3 / 5
	Total	14 / 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.

The description is strong: it states concrete capabilities and provides an explicit, natural-language "Use when" trigger clause covering the main Fargate use cases. It is comprehensive and clearly scoped to AWS Fargate on ECS with only minor distinctiveness overlap against related ECS skills.

Dimension	Reasoning	Score
Specificity	"Covers Fargate vs EC2 decision guide, CPU/memory sizing, platform versions, Fargate Spot cost optimization, Graviton/ARM architecture, networking, and EFS integration" lists multiple specific concrete topics with comprehensive coverage, matching the anchor-5 example.	5 / 5
Completeness	It explicitly states both what it does ("AWS Fargate serverless container compute for ECS. Covers...") and when to use it ("Use when deploying serverless containers, optimizing Fargate costs, sizing Fargate tasks, or choosing between Fargate and EC2 launch types"), matching the anchor-5 what-and-when pattern with concrete trigger phrases.	5 / 5
Trigger Term Quality	"deploying serverless containers, optimizing Fargate costs, sizing Fargate tasks, or choosing between Fargate and EC2 launch types" are natural phrases users would say, with good keyword coverage, but a few synonyms (e.g. "AWS", "ECS tasks", "container compute") are absent so it falls just short of anchor 5.	4 / 5
Distinctiveness Conflict Risk	The Fargate-for-ECS niche is clear with distinct triggers, but "deploying serverless containers" and the broader ECS topic create minor overlap risk with sibling skills like ecs-deployment and terraform-ecs, keeping it just below anchor 5.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/ecs-fargate/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.