Skip to content
Back to search

sample-apex-skills

Curated agentic AI skills for AWS platform engineering, starting with Amazon EKS and Amazon ECS, delivered through any coding agent

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/aws-samples/sample-apex-skills with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/aws-samples/sample-apex-skills'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aws-samples--sample-apex-skills/badge.svg)](/listings/aws-samples--sample-apex-skills)

HTML

<a href="/listings/aws-samples--sample-apex-skills"><img src="/api/listings/aws-samples--sample-apex-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

NPX Installer (recommended)

> **Prerequisites:** [Node.js 18+](https://nodejs.org/) and [git](https://git-scm.com/) must be installed.

npx apex-skills@1.3.0

APEX v2 is in progress, so the commands here pin the installer to exactly version 1.3.0 until v2 ships, which also skips later 1.3.x installer releases. A fresh install with no earlier install record takes the newest v1.x.y release of the skills; `--version` picks a release, `--branch` follows a branch, and `--update` stays on the clone's major line or the branch it follows.

The installer's own messages show `npx apex-skills`; add `@1.3.0` when you run them.

For v2 and its `/apex` router, use the Manual Install below (from `main`).

Detects Claude Code and/or Kiro CLI, clones the repo to `~/.apex-skills/`, and links the skills into place. Flags, exit codes, [installed paths](misc/installer/README.md#installed-paths) and [uninstall](misc/installer/README.md#uninstall): see the [installer README](misc/installer/README.md).

Before upgrading from installer 1.2.0 or earlier, and before re-running after moving or renaming a home or project directory, copy out edited Kiro steering copies and remove or note links of your own into `~/.apex-skills`: with no install record the installer cannot tell them from its own.

npx apex-skills@1.3.0 --update              # Update an existing install
npx apex-skills@1.3.0 --version v1.2.0      # Installer 1.3.0, skills release v1.2.0
npx apex-skills@1.3.0 --branch feat/new-eks # Install from a branch
npx apex-skills@1.3.0 --help                # See all options

Manual Install

If you prefer not to use npx, clone the repo and copy skills directly.

Claude Code

git clone https://github.com/aws-samples/sample-apex-skills.git
cd sample-apex-skills

mkdir -p ~/.claude/skills
cp -r skills/* ~/.claude/skills/

**Usage (this manual install, from `main`):** Start a Claude Code session and type `/apex` with your request (for example *"Help me design an EKS cluster"* or *"Is my cluster ready to upgrade to 1.32?"*): the apex skill routes it to the right skill and, when there is one, that skill's runbook.

Kiro CLI

git clone https://github.com/aws-samples/sample-apex-skills.git
cd sample-apex-skills

mkdir -p ~/.kiro/skills
cp -r skills/* ~/.kiro/skills/

**Usage:** in Kiro, type `/apex` with your request, or ask for apex by name, for example *"use apex to plan my EKS upgrade"*. Tested on Kiro CLI 2.35.1 (2026-10-28); Kiro CLI 1.27.0 rejected `/apex`.

Codex

git clone https://github.com/aws-samples/sample-apex-skills.git
cd sample-apex-skills

mkdir -p ~/.agents/skills
cp -r skills/* ~/.agents/skills/

**Usage:** in Codex, type `$apex` with your request, for example *"$apex plan my EKS upgrade"*. Codex reads skills from `~/.agents/skills` (and a repository's `.agents/skills`); the installer does not set up Codex.

Other Agent Harnesses

Skills follow the [Agent Skills standard](https://agentskills.io/). Each skill lives in `skills/{skill-name}/` with a `SKILL.md` and optional `references/`, `scripts/`, and `assets/` directories. Clone and point your tool at them — see [skills/README.md](skills/README.md) for the layout.

Agent Rules (optional)

[AGENTS.md](./rules/AGENTS.md) contains project-level guardrails: skill routing, verification habits, source-checking, safety boundaries. These are personal to each user's workflow, so they are **not** auto-loaded by the installer. To activate them, add the contents to whatever file your agent harness reads for project instructions (e.g., `CLAUDE.md`, `AGENTS.md`, `.cursorrules`, `.github/copilot-instructions.md`, `.kiro/steering/project.md`).

The apex skill's shared rules apply to runs it starts; a skill triggered directly follows its own rules, plus AGENTS.md if you added it.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 209 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <img src="misc/website/static/img/logo.svg" alt="APEX Skills" width="120">
  3. # APEX Skills
  4. **Platform engineering with agents: curated AWS skills for Amazon EKS and Amazon ECS, delivered through your AI coding agent.**
  5. [![Docs](https://img.shields.io/badge/docs-GitHub%20Pages-blue)](https://aws-samples.github.io/sample-apex-skills/)
  6. [![npm](https://img.shields.io/npm/v/apex-skills)](https://www.npmjs.com/package/apex-skills)
  7. [![License: MIT-0](https://img.shields.io/badge/license-MIT--0-green)](LICENSE)
  8. [![docs-sync](https://github.com/aws-samples/sample-apex-skills/actions/workflows/docs-sync.yml/badge.svg)](https://github.com/aws-samples/sample-apex-skills/actions/workflows/docs-sync.yml)
  9. [Docs](https://aws-samples.github.io/sample-apex-skills/) · [Find a skill](https://aws-samples.github.io/sample-apex-skills/skills/) · [Getting started](https://aws-samples.github.io/sample-apex-skills/docs/getting-started/) · [Contributing](CONTRIBUTING.md)
  10. </div>
  11. ## What APEX is
  12. - **Skills**: what your agent knows. 28 skills, written to the [Agent Skills standard](https://agentskills.io/), that design, build, review, upgrade and secure Amazon EKS and Amazon ECS estates.
  13. - **The `/apex` router** (installed from `main`, below): one entry point. Type `/apex` with your request and it picks the right skill, or follows a runbook you name: your own procedure that chains skills.
  14. - **DevOps Agent ports**: 6 Day 2 skills repackaged for [AWS DevOps Agent](https://docs.aws.amazon.com/devopsagent/latest/userguide/).
  15. Domain knowledge by AWS Solutions Architects, TAMs and ProServe. 5 skills are vendored from upstream projects; see [Provenance](#provenance).
  16. ## Quick start
  17. You need [Node.js 18+](https://nodejs.org/) and [git](https://git-scm.com/), on macOS or Linux (on Windows, use WSL).
  18. ```bash
  19. npx apex-skills@1.3.0
  20. ```
  21. The installer detects Claude Code and Kiro CLI, clones the repo to `~/.apex-skills/` and links the skills into place. It installs the latest published release of the skills. The skill list below describes `main`. The latest published release does not have the `/apex` router yet, has older versions of some skills and still has steering-workflow-creator, which `main` drops, so install from `main` (below) to get everything listed here.
  22. Ask your agent in plain words and the matching skill loads:
  23. > Is my EKS cluster ready to upgrade to 1.32?
  24. In Claude Code this install also adds `/apex:*` commands, such as `/apex:eks-upgrade-check`; Kiro CLI gets the workflows, without the `eks` hub, as manual steering files in `~/.kiro/steering/`.
  25. Flags, updates and uninstall: [installer README](misc/installer/README.md).
  26. ### The `/apex` router
  27. To use the router in Claude Code or Kiro CLI, install from `main` (this also moves an existing install to `main`, which has no `/apex:*` commands or Kiro steering files):
  28. ```bash
  29. npx apex-skills@1.3.0 --branch main
  30. ```
  31. Then type your request after the router:
  32. > /apex is my cluster ready to upgrade to 1.32?
  33. For Codex, which the installer does not set up, copy the skills by hand:
  34. ```bash
  35. git clone https://github.com/aws-samples/sample-apex-skills.git
  36. mkdir -p ~/.agents/skills && cp -r sample-apex-skills/skills/* ~/.agents/skills/
  37. ```
  38. In Codex the router is `$apex`. `/apex` in Kiro CLI was tested on 2.35.1 (2026-10-28); 1.27.0 rejected it. Other harnesses: [Getting started](https://aws-samples.github.io/sample-apex-skills/docs/getting-started/). [classes/](classes/) holds the shared rules; the class sync (`misc/sync-classes.py`) copies them into each skill that joins a class.
  39. ## See it work
  40. The [EKS Upgrade Readiness Check](examples/eks-upgrades/in-place-karpenter-check/) example, run in Claude Code:
  41. | The agent finds your clusters | The scored result |
  42. |---|---|
  43. | ![Cluster discovery](examples/eks-upgrades/in-place-karpenter-check/static/cc/02-cluster-discovery.png) | ![Assessment result](examples/eks-upgrades/in-place-karpenter-check/static/cc/04-assessment-result.png) |
  44. ## How it fits
  45. ```mermaid
  46. flowchart LR
  47. U[You] --> H[Agent harness<br/>Claude Code, Kiro CLI, Codex]
  48. H --> R["/apex router"]
  49. R --> S[Skill]
  50. S --> T["AWS CLI, kubectl or MCP servers,<br/>when the skill needs them"]
  51. T --> O[Report or code]
  52. ```
  53. ## Pick a skill by what you are doing
  54. Not sure? Use [`/apex`](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/apex/) (installed from `main`) and it picks for you.
  55. <!-- SKILLS_REFERENCE_START -->
  56. > _This list is auto-generated by [`misc/update-skills-references.sh`](misc/update-skills-references.sh) from the SKILL_META table in [`misc/update-pages.sh`](misc/update-pages.sh). Do not edit manually._
  57. ### Knowledge Skills
  58. Guidance your agent draws on when you ask and decide.
  59. | Skill | What it does |
  60. |---|---|
  61. | [ecs-genai](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-genai/) | GPU, ML and GenAI workloads on ECS: GPU instances, Inferentia, Trainium and Neuron, launch type choice, training and model inference |
  62. | [eks-best-practices](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-best-practices/) | EKS architecture advice: compute, networking, security, reliability, cost, scaling, observability, multi-tenancy, upgrades, hybrid and surge readiness |
  63. ### Day 0 Design
  64. Choose an architecture before you build.
  65. | Skill | What it does |
  66. |---|---|
  67. | [ecs-architect](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-architect/) | Choose the ECS compute model for a new workload: Fargate, EC2, Managed Instances, Express Mode or ECS Anywhere, plus capacity providers and task sizing |
  68. | [ecs-observability](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-observability/) | ECS observability architecture: logs, metrics and traces with CloudWatch, Container Insights, X-Ray, ADOT, Managed Prometheus and Grafana, or FireLens |
  69. | [eks-design](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-design/) | Generate EKS architecture design documents with Mermaid diagrams, ADRs, security architecture and validation reports, guided by Well-Architected practices |
  70. ### Day 1 Build
  71. Generate the infrastructure code and the release path.
  72. | Skill | What it does |
  73. |---|---|
  74. | [dotnet-aws-ecs](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/dotnet-aws-ecs/) | Deploy a .NET workload to Amazon ECS Fargate behind an Application Load Balancer, with CloudFormation or CDK and a deployment guide |
  75. | [ecs-build](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-build/) | Generate apply-ready Terraform for ECS clusters, services and task definitions on Fargate, EC2 Auto Scaling or Managed Instances |
  76. | [ecs-devops](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-devops/) | Deploy and release to ECS: blue/green and canary deployments, CI/CD pipelines and rollbacks |
  77. | [eks-build](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-build/) | Generate production-ready EKS Terraform projects with optional ArgoCD GitOps, air-gapped support and 29+ addon configurations |
  78. | [eks-genai](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-genai/) | GenAI and LLM workloads on EKS: GPU vs Trainium/Inferentia, vLLM and Ray serving, distributed training, ML storage and AI gateways |
  79. | [eks-platform-engineering](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-platform-engineering/) | Internal Developer Platform design on EKS: Backstage, ArgoCD, Kargo, progressive delivery, golden paths and DORA metrics |
  80. | [terraform-skill](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/terraform-skill/) | Terraform and OpenTofu: modules, native tests, Terratest, CI/CD pipelines, state debugging and security scanning |
  81. ### Day 2 Operate: assess what is running
  82. Discover, score and review a live cluster or estate.
  83. | Skill | What it does |
  84. |---|---|
  85. | [ecs-operation-review](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-operation-review/) | Structured ECS operational excellence assessment of a live estate across 8 domains with GREEN/AMBER/RED ratings |
  86. | [ecs-recon](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-recon/) | ECS environment discovery: compute and capacity providers, task definitions, scaling, networking, security, observability and IaC/CI-CD |
  87. | [eks-cost-intelligence](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-cost-intelligence/) | Live EKS cost efficiency assessment across 6 dimensions with a 0-100 Cost Score and dollar-quantified findings |
  88. | [eks-operation-review](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-operation-review/) | EKS operational excellence assessment across 10 areas, GREEN/AMBER/RED rated, with prioritized recommendations and deprecated-API review with no target version |
  89. | [eks-recon](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-recon/) | EKS cluster discovery: compute, networking, security facts, add-ons, workloads, storage, IaC and CI/CD, reported as facts |
  90. | [eks-well-architected-review](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-well-architected-review/) | Unofficial, deterministic Well-Architected style review of a live EKS cluster (Linux nodes only) across five pillars; run only on an explicit WAFR request |
  91. ### Day 2 Operate: upgrade and migrate
  92. Move a version, a controller, a CPU architecture or an app.
  93. | Skill | What it does |
  94. |---|---|
  95. | [ecs-modernize](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-modernize/) | Assess an existing VMware or EC2 app from its source code, decide replatform or rearchitect, and migrate it onto ECS |
  96. | [eks-ingress-migration](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-ingress-migration/) | Assess a live cluster's NGINX/Ingress estate and plan migration to Gateway API, the AWS Load Balancer Controller or AWS Transform |
  97. | [eks-upgrade-check](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-upgrade-check/) | Assess EKS cluster upgrade readiness with a 0-100 score across 8 areas including deprecated APIs, add-on compatibility and workload risks |
  98. | [graviton-migration](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/graviton-migration/) | Migrate a workload from x86 to AWS Graviton (arm64): arm64 readiness scanning with the Arm migration MCP server, then the Karpenter node cutover on EKS |
  99. ### Day 2 Operate: secure
  100. Check exposure, harden and prepare for audits.
  101. | Skill | What it does |
  102. |---|---|
  103. | [ecs-security](https://aws-samples.github.io/sample-apex-skills/docs/skills/ecs/ecs-security/) | ECS security and compliance: task and execution roles, iam:PassRole, trust policies, secrets injection and shared responsibility on Fargate and EC2 |
  104. | [eks-security](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-security/) | Read-only scripted reviews of a live cluster (CVEs, events, posture); hardening: CIS, HIPAA, PCI-DSS, FedRAMP, SOC 2, GuardDuty, Pod Identity, image signing |
  105. ### Set up and extend
  106. Connect tools, write your own skills, keep docs in sync.
  107. | Skill | What it does |
  108. |---|---|
  109. | [apex-new-skill](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/apex-new-skill/) | Add a new skill or a class change to the APEX repo: classes, SKILL_META line, eval set, generators, CI checks, ADR, design-doc note and pull request |
  110. | [apex](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/apex/) | Router for EKS and ECS requests: picks the skill that fits, infers the stage (Day 0 Design, Day 1 Build, Day 2 Operate), carries context, suggests next skills |
  111. | [eks-mcp-server](https://aws-samples.github.io/sample-apex-skills/docs/skills/eks/eks-mcp-server/) | Set up and troubleshoot the EKS MCP Server in your AI assistant; for cluster work once MCP works, use eks-recon, eks-operation-review or eks-upgrade-check |
  112. | [skill-creator](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/skill-creator/) | Create new skills, modify existing skills, run evals, benchmark performance and optimize triggering accuracy |
  113. | [update-docs](https://aws-samples.github.io/sample-apex-skills/docs/skills/general/update-docs/) | Audit and sync all documentation surfaces after skill changes: README markers, Docusaurus site and prose references |
  114. <!-- SKILLS_REFERENCE_END -->
  115. <!-- EXAMPLES_REFERENCE_START -->
  116. ## Examples
  117. > _This table is auto-generated by [`misc/update-examples-references.sh`](misc/update-examples-references.sh). Do not edit manually._
  118. | Example | Description | Workflow |
  119. |---------|-------------|----------|
  120. | **[Liberty to ECS Modernization](examples/ecs-modernize/liberty-to-ecs/)** | Assess a Java 8 / WebSphere Liberty application carrying planted modernization blockers, score it with the APEX ecs-modernize skill, then execute both migration paths on ECS — Replatform as-is onto ECS on EC2 and Rearchitect onto Fargate — and re-assess to see the Fit_Score rise from the Replatform band into the Rearchitect band. | -- |
  121. | **[EKS Upgrade Readiness Check](examples/eks-upgrades/in-place-karpenter-check/)** | Deploy an EKS 1.32 cluster with Karpenter v1.0.2 and planted upgrade issues, then run the APEX EKS upgrade-check skill to produce a scored readiness report showing NOT READY status. | [eks-upgrade-check](skills/eks-upgrade-check/SKILL.md) |
  122. <!-- EXAMPLES_REFERENCE_END -->
  123. ## DevOps Agent
  124. 6 Day 2 skills (eks-cost-intelligence, eks-ingress-migration, eks-operation-review, eks-recon, eks-security, eks-upgrade-check) are ported for managed autonomous runs in AWS DevOps Agent: see [devops-agent/](devops-agent/README.md).
  125. ## Provenance
  126. 5 skills are vendored from upstream and synced by `misc/sync-*.sh`; do not edit them here. Three carry small sync-time edits, listed in each skill's UPSTREAM.md.
  127. | Skill | Upstream | License |
  128. |---|---|---|
  129. | skill-creator | [anthropics/skills](https://github.com/anthropics/skills) | Apache 2.0 |
  130. | terraform-skill | [antonbabenko/terraform-skill](https://github.com/antonbabenko/terraform-skill) | Apache 2.0 |
  131. | dotnet-aws-ecs | [adisimon217/sample-appmod-skills](https://github.com/adisimon217/sample-appmod-skills) | MIT |
  132. | eks-operation-review | [aws-samples/sample-eks-operation-review-skill](https://github.com/aws-samples/sample-eks-operation-review-skill) | MIT-0 |
  133. | eks-upgrade-check | [aws-samples/sample-eks-upgrade-skill](https://github.com/aws-samples/sample-eks-upgrade-skill) | MIT-0 |
  134. Details: [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md) and the UPSTREAM.md of [dotnet-aws-ecs](skills/dotnet-aws-ecs/UPSTREAM.md), [eks-operation-review](skills/eks-operation-review/UPSTREAM.md) and [eks-upgrade-check](skills/eks-upgrade-check/UPSTREAM.md).
  135. ## Contributing
  136. See [CONTRIBUTING.md](CONTRIBUTING.md) for adding skills, runbooks and examples. Security issues: [CONTRIBUTING.md, Security Issue Notifications](CONTRIBUTING.md#security-issue-notifications).
  137. ## Disclaimer
  138. Sample code for **educational and demonstration purposes only**. It is not intended for direct production use without proper review, testing, and validation. Test generated infrastructure (Terraform, Helm charts, kubectl commands) in non-production environments first. Use at your own risk: the authors are not responsible for any issues, damages, or losses that may result from using this code in production.
  139. ## License
  140. This project is licensed under the MIT-0 License. See the [LICENSE](LICENSE) file.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.