boto3-ecs

AWS Boto3 SDK patterns for Amazon ECS cluster management, task definitions, services, and Fargate deployments. Use when working with ECS clusters, managing task definitions, deploying services, running one-off tasks, monitoring deployments, or integrating ECS with Python applications.

Quality

82%

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

Quality

Content

76%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 highly actionable, code-rich ECS reference with well-organized sections and a clear progressive-disclosure map to real bundle files. Its main weaknesses are the absence of validation/feedback checkpoints around destructive operations and some inlined API reference and redundancy that slightly bloat the overview.

Suggestions

Add explicit validation steps around destructive operations — e.g., after scaling a service to 0, verify desiredCount==runningCount before calling delete_service; after stop_task, confirm the task reached STOPPED via describe_tasks or a waiter.

Move the fuller create_service / register_task_definition examples into the corresponding reference files and keep only a minimal quick-start snippet inline to reduce overview length and redundancy.

Collapse the duplicate create_service block by showing one canonical example and noting the launchType-vs-capacityProviderStrategy swap as a one-line variant.

Dimension	Reasoning	Score
Conciseness	Mostly lean, code-dense content that assumes Claude's competence, with minor redundancy such as create_service shown twice (launchType vs capacityProviderStrategy) and a 'Complete patterns for...' intro line that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready Boto3 code throughout — client init, cluster/task/service CRUD, run_task, error handling, waiters, and a deployment monitor function — covering the common cases concretely.	5 / 5
Workflow Clarity	Content is organized by topic rather than as a sequenced workflow, and destructive/batch operations (delete_service scale-to-zero then delete, stop_task) lack explicit validation checkpoints, which caps workflow clarity at 3 per the destructive-ops rule.	3 / 5
Progressive Disclosure	A dedicated 'Progressive Disclosure' section signals one-level-deep references to the three real reference files (cluster-operations.md, task-definitions.md, service-management.md), though a fair amount of full API-reference code is inlined in the overview that could live in those files.	4 / 5
	Total	16 / 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, third-person description that concretely names capabilities and provides explicit 'Use when...' trigger guidance covering the main ECS use cases. Minor overlap with sibling ECS skills and a few missing synonyms keep it just short of perfect.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'cluster management, task definitions, services, and Fargate deployments' plus 'managing task definitions, deploying services, running one-off tasks, monitoring deployments' — giving comprehensive coverage of the ECS domain.	5 / 5
Completeness	Explicitly answers both what ('AWS Boto3 SDK patterns for Amazon ECS...') and when ('Use when working with ECS clusters, managing task definitions, deploying services...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('ECS clusters', 'task definitions', 'deploying services', 'Fargate', 'one-off tasks', 'Python applications') that users would actually say, though a few synonymous phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Boto3/Python for ECS) with distinct triggers, but minor overlap risk with closely related ecs-fargate and ecs-deployment skills acknowledged in the body.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

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