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

82%

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

The canonical home for this skill is aws-containers in aws/agent-toolkit-for-aws

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-architected hub skill: the routing table, MCP-vs-local guardrail, freshness caveat, and proactive ECS Action Logs trigger are all genuinely useful and clearly signaled, and the full bundle is coherent with all referenced files present. The main cost is the Services section, which pads the body with marketing-style explanations of EKS/ECS/ECR/Beanstalk that Claude already knows, and the two-hop reference structure that hides topic-level routing inside the hub files.

Suggestions

Cut the Services section's marketing copy (e.g., "EKS is the premier platform for running Kubernetes clusters", the ECS "focus on building the applications, not the environment" paragraph) down to one-line definitions, or fold them into the routing table rows — Claude already knows what these services are.

Surface the second-level topic triggers from the hub files (load balancers/ingress, GPU sharing, task definitions, VPC CNI, ECS Gateway, Beanstalk configuration/platforms) directly in the SKILL.md routing table so topic-level needs resolve in one hop instead of two.

Drop the EKS benefit bullets ("Deploy applications faster with less operational overhead", "Scale seamlessly to meet changing workload demands"), which add no routing or actionability value and duplicate the description.

DimensionReasoningScore

Conciseness

The operational core is tight (routing table, MCP-vs-local guardrail, staleness note, proactive Action Logs trigger), but the Services section spends several paragraphs explaining 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" and "EKS is the premier platform for running Kubernetes clusters" are vendor marketing copy. This lands between anchor 2's "several unnecessary explanations" and the mostly-efficient anchor 3; the useful routing content dominates, so 3.

3 / 5

Actionability

Gives concrete, executable routing guidance: a need-to-file table, exact fetch instructions ("You MUST fetch each reference via `retrieve_skill` with the `file` parameter (e.g. `file=\"references/ecs.md\"")"), named tools ("aws___read_documentation and aws___search_documentation"), and a specific proactive trigger to "read action-logs.md before responding and follow its tiering". Not 5 because the body itself contains no commands or code — the executable detail lives one file away — which is acceptable for an instruction/routing skill but leaves minor gaps against the copy-paste-ready anchor.

4 / 5

Workflow Clarity

The sequence is clear and correctly ordered: first "Determine how the skill was loaded before reading a reference file" (with both branches spelled out), then route via the table, then "always read the relevant reference file before responding". Anchor 5's explicit validation steps and feedback loops don't genuinely apply to a non-destructive routing skill, but there are no risky operations requiring them, so this sits at anchor 4 with only minor gaps (e.g., no explicit fallback if a routed file lacks the answer).

4 / 5

Progressive Disclosure

SKILL.md is a clean overview with a well-signaled routing table, and every referenced file (eks.md, ecs.md, ecr.md, beanstalk.md, action-logs.md) exists in references/. However, references are two levels deep rather than one: the hub files route onward (e.g., ecs.md → ecs-workloads.md / ecs-gateway.md / ecs-gpu-sharing.md; eks.md → eks-load-balancer-controller.md / eks-networking.md), so topic-level needs like "load balancers" require two hops. Good structure with a minor organization gap versus the one-level-deep anchor at 5; far from the buried/impossible-navigation anchors at 1-2.

4 / 5

Total

15

/

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: third-person voice, explicit what-and-when structure with concrete trigger phrases, and comprehensive service- and feature-level keywords for the AWS containers domain. Its main weaknesses are the repetitive "Covers general X knowledge" padding, which dilutes the concrete action statements, and a couple of missing natural synonyms such as "Docker".

DimensionReasoningScore

Specificity

Lists several concrete actions — "Builds and deploys containerized workloads", "recommending, enabling, and reading Amazon ECS Action Logs to troubleshoot control-plane failures", "ECR repository setup and lifecycle policies" — but interleaves them with topic enumerations ("Covers general EKS knowledge", "Covers general Elastic Beanstalk knowledge") that are not concrete actions, so it falls short of the comprehensive pure-action anchor at 5 and well above the 1-2-action anchor at 3.

4 / 5

Completeness

Explicitly answers both questions: what ("Builds and deploys containerized workloads on Elastic Kubernetes Service (EKS), Elastic Container Service (ECS), Fargate, and ECR") and when ("Applies when deploying, debugging, or optimizing containers on AWS") with concrete trigger phrases, matching the anchor 5 example structure; anchor 4's "when could be more explicit" does not apply.

5 / 5

Trigger Term Quality

Good keyword coverage of terms users naturally say: "EKS", "ECS", "Fargate", "Karpenter", "task definitions", "ECS Exec", "lifecycle policies", and the explicit trigger phrase "deploying, debugging, or optimizing containers on AWS". A few common natural terms are missing (e.g., "Docker", standalone "Kubernetes cluster" phrasing), which keeps it below the comprehensive-with-synonyms anchor at 5 but comfortably above anchor 3.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — the named AWS container services ("Elastic Kubernetes Service (EKS), Elastic Container Service (ECS), Fargate, and ECR") plus feature-specific terms like "ECS Express Mode" and "Amazon ECS Action Logs" make accidental triggering of an unrelated skill unlikely; no generic phrasing that would conflict broadly.

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

plugins/aws-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.