CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-containers

Builds and deploys containerized workloads on Elastic Kubernetes Service (EKS), Elastic Container Service (ECS), Fargate, and ECR (Elastic Container Registry). Covers general EKS knowledge, Karpenter, AWS Load Balancer Controller and leveraging various open source Kubernetes projects with EKS. Covers general ECS knowledge, task definitions, Fargate services, ECS Exec, ECS Express Mode and ECS Managed Instances. Covers general Elastic Beanstalk knowledge, Elastic Beanstalk configuration and platforms supported by Elastic Beanstalk. Covers general ECR knowledge, ECR repository setup and lifecycle policies. Includes recommending, enabling, and reading Amazon ECS Action Logs to troubleshoot control-plane failures (deployment rollback/circuit-breaker, task placement, scaling, task replacement). Applies when deploying, debugging, or optimizing containers on AWS. Should be used instead of relying on internal knowledge for these services.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/core-skills/aws-containers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 excels as a routing document: the MCP-vs-local guardrail, keyword-driven routing table, and conditional Action Logs trigger give Claude unambiguous next actions, and the bundle structure is well organized. Its main liability is token efficiency — the Services section re-explains EKS/ECS/ECR/Beanstalk in marketing prose that adds no capability or routing value.

Suggestions

Collapse the Services section to a one-line service list or fold it into the routing table — the multi-paragraph descriptions of EKS, ECS, ECR, and Elastic Beanstalk restate concepts Claude already knows.

Delete the benefit bullets under EKS ('Deploy applications faster with less operational overhead', 'Scale seamlessly...'), which are pure marketing copy with no actionable content.

Consider surfacing a few high-value sub-reference keywords (GPU sharing, ECS Gateway, VPC CNI, load balancer controller) in the top-level routing table so common needs route in one hop instead of two.

DimensionReasoningScore

Conciseness

The Services section spends roughly a third of the body on vendor-style explanations of concepts Claude already knows — 'Amazon Elastic Container Service (Amazon ECS) is a fully managed container orchestration service that helps you easily deploy, manage, and scale containerized applications', plus marketing bullets like 'Deploy applications faster with less operational overhead' and 'Scale seamlessly to meet changing workload demands'. That matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than score 3's 'some unnecessary explanation', since all four service subsections repeat this pattern; the routing, guardrail, and MCP guidance elsewhere are efficient.

2 / 5

Actionability

Concrete, executable direction throughout: the routing table maps each user need to a specific file ('Elastic Container Service (ECS)' → 'Read ecs.md'), the guardrail gives exact mechanics ('fetch each reference via retrieve_skill with the file parameter (e.g. file="references/ecs.md")'), and the Action Logs rule specifies a conditional action. Not 5 because the top level contains no commands or examples itself — all executable procedures live in the reference files — leaving minor gaps at the SKILL.md level.

4 / 5

Workflow Clarity

The sequence is clear: determine how the skill was loaded ('Determine how the skill was loaded before reading a reference file'), route the user need via the table, then 'always read the relevant reference file before responding'; the proactive Action Logs recommendation adds a conditional checkpoint ('read action-logs.md before responding'). Not 5 because there are no explicit verification or error-recovery steps (e.g., what to do when a reference is unavailable), though this knowledge-routing skill involves no destructive or batch operations that would mandate them.

4 / 5

Progressive Disclosure

SKILL.md is a lean hub with a keyword-driven routing table, and every referenced file (eks.md, ecs.md, ecr.md, beanstalk.md, action-logs.md) exists in the bundle, with the hub files in turn giving clear keyword routing to detail files. Not 5 because references are effectively two levels deep (SKILL.md → service hub → detail files such as eks-control-plane.md and ecs-workloads.md), and the top-level routing table exposes only 4 of the 17 reference files — good structure with minor organization gaps rather than the ideal one-level-deep layout.

4 / 5

Total

14

/

20

Passed

Description

87%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: it names concrete capabilities across specific AWS container services and includes an explicit 'Applies when...' trigger clause in third-person voice. The main weakness is padding — 'Covers general X knowledge' phrasing repeated per service inflates length without adding concrete capability or trigger value.

DimensionReasoningScore

Specificity

Lists several concrete actions across named services — 'Builds and deploys containerized workloads on Elastic Kubernetes Service (EKS), Elastic Container Service (ECS), Fargate, and ECR', 'ECR repository setup and lifecycle policies', 'recommending, enabling, and reading Amazon ECS Action Logs to troubleshoot control-plane failures (deployment rollback/circuit-breaker, task placement...)'. Falls short of 5 because repeated filler like 'Covers general EKS knowledge' and 'Covers general Elastic Beanstalk knowledge' is abstract rather than a concrete capability, and is above 3 because the action list is broad and specific (task definitions, ECS Exec, lifecycle policies, Karpenter).

4 / 5

Completeness

Explicitly answers both what ('Builds and deploys containerized workloads on EKS, ECS, Fargate, and ECR... troubleshooting control-plane failures') and when ('Applies when deploying, debugging, or optimizing containers on AWS') with concrete trigger verbs. The 'Should be used instead of relying on internal knowledge for these services' clause reinforces the when, matching the anchor rather than the score-4 case where the when is only loosely specified.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would actually say: EKS, ECS, Fargate, ECR, Elastic Beanstalk, Karpenter, task definitions, ECS Exec, 'deploying, debugging, or optimizing containers on AWS'. Not 5 because common phrasings like 'Kubernetes on AWS', 'Docker images', or generic 'container registry' are missing; not 3 because the service names and sub-features go well beyond a bare domain mention.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear AWS-containers niche with distinct named-service triggers (EKS, ECS, Fargate, ECR, Elastic Beanstalk, ECS Action Logs), so it is unlikely to fire for non-AWS Kubernetes/Docker work or unrelated AWS skills. Third-person voice ('Builds and deploys') is used throughout.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

aws/agent-toolkit-for-aws

Path

skills/core-skills/aws-containers/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.