AF aws-containers
Deploys and operates containerized workloads on ECS, Fargate, and ECR. Covers task definitions, Fargate services, ECR repository setup and lifecycle policies, ECS Exec debugging, service scaling, deployment strategies, load balancer integration, and logging configuration. Use when deploying, debugging, or optimizing containers on AWS. ALSO USE for container deployment options (ECS vs ECS Express Mode), networking modes, health check troubleshooting, OOM errors, secrets injection, blue/green deployments, ECR image management, and App Runner sunset guidance and migration. NOT for Kubernetes, EKS, or CI/CD pipelines.
Deploys and operates containerized workloads on ECS, Fargate, and ECR.
As a process F 52/100 · Will not run — References files that are not bundled: references/task-definition-authoring.md, references/fargate-service-deployment.md, references/ecr-repository-management.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/task-definition-authoring.md - warning
missing-refreference to a missing file: references/fargate-service-deployment.md - warning
missing-refreference to a missing file: references/ecr-repository-management.md - warning
missing-refreference to a missing file: references/ecs-exec-debugging.md - warning
missing-refreference to a missing file: references/service-scaling-and-updates.md - warning
missing-refreference to a missing file: references/app-runner-guide.md - warning
missing-refreference to a missing file: references/ecs-infrastructure-patterns.md - warning
missing-refreference to a missing file: references/ecs-logging-and-firelens.md - warning
missing-refreference to a missing file: references/ecs-troubleshooting-guide.md - warning
missing-refreference to a missing file: references/fargate-spot.md - note
edit-residuethe text marks something as outdated (lines 56, 86): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/100
- 0Tools and files. 10 referenced file(s) missing: references/task-definition-authoring.md, references/fargate-service-deployment.md, references/ecr-repository-management.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 35 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4994 tokens
- 85Steps. 64 steps, 1 vague phrases
- 100Failures and branches. 12 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 621: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 64 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.