Curated platform-engineering skills that compress onboarding from months to weeks. Domain knowledge authored by senior AWS SSAs, TAMs, and ProServe, delivered through agentic AI tools (Claude Code, Kiro CLI etc).
APEX uses agentic AI (frontier models and agent harness like Claude Code) combined with curated "skills" to give engineers SSA-grade platform engineering output.
Agent Skills are organized folders of instructions, scripts, and resources that frontier LLM models can discover and load dynamically to perform specialized tasks. By codifying expert platform engineering knowledge as Agent Skills, we amplify best practices and scale them across teams while reducing toil. They follow the Agent Skills Agent Skills open standard open standard and are compatible with any supported agent harness.
| Directory | Purpose |
|---|---|
skills/ |
What the agent knows — reusable domain knowledge |
steering/ |
How the agent runs an engagement — slash commands, questionnaires, routing |
rules/ |
How the agent behaves — verification, source-checking, guardrails |
examples/ |
How to try it — deployable labs with planted issues |
misc/ |
Maintenance tooling and evaluation framework |
Prerequisites: Node.js 18+ and git must be installed.
npx apex-skillsDetects Claude Code and/or Kiro CLI, clones the repo to ~/.apex-skills/, and symlinks all skills + steering into the right locations.
npx apex-skills --update # Pull latest skills
npx apex-skills --version v1.2.0 # Pin to a specific release
npx apex-skills --branch feat/new-eks # Install from a branch
npx apex-skills --help # See all optionsIf you prefer not to use npx, clone the repo and copy skills directly.
git clone https://github.com/aws-samples/sample-apex-skills.git
cd sample-apex-skills
mkdir -p ~/.claude/skills ~/.claude/commands
cp -r skills/* ~/.claude/skills/
ln -sfn "$(pwd)/steering/commands/apex" ~/.claude/commands/apex
ln -sfn "$(pwd)/steering" ~/.claude/apex-steeringUsage: Start a Claude Code session and use slash commands:
/apex:eks— hub that auto-routes based on your request/apex:eks-design— "Help me design an EKS cluster"/apex:eks-upgrade-check— "Is my cluster ready to upgrade to 1.32?"
git clone https://github.com/aws-samples/sample-apex-skills.git
cd sample-apex-skills
mkdir -p ~/.kiro/skills ~/.kiro/steering
cp -r skills/* ~/.kiro/skills/
cp steering/workflows/*.md ~/.kiro/steering/Skills follow the Agent Skills standard. 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 for the layout.
AGENTS.md contains project-level guardrails — 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).
This table is auto-generated by
misc/update-skills-references.sh. Do not edit manually.
| eks-best-practices | eks-build | eks-cost-intelligence | eks-design |
| eks-genai | eks-ingress-migration | eks-mcp-server | eks-operation-review |
| eks-platform-engineering | eks-recon | eks-security | eks-upgrade-check |
(coming soon)
| skill-creator | steering-workflow-creator | terraform-skill | update-docs |
This table is auto-generated by
misc/update-steering-references.sh. Do not edit manually.
| apex | eks | design | eks-build |
| eks-genai | eks-operation-review | eks-platform-engineering | eks-security |
| eks-upgrade-check | new-skill |
| /apex:eks-build | /apex:eks-design | /apex:eks-genai |
| /apex:eks-operation-review | /apex:eks-platform-engineering | /apex:eks-security |
| /apex:eks-upgrade-check | /apex:eks | /apex:new-skill |
Steering files define how the agent runs an engagement. Structured sequences with questionnaires, checkpoints, and routing. The hub (/apex:eks) detects what you want and routes to the right workflow. Slash commands (e.g., /apex:eks-design) are agent-harness entry points that trigger these workflows.
The key test: Remove all steering files and the agent still knows the right answers (skills provide knowledge). But it wouldn't know how to run the engagement.
This table is auto-generated by
misc/update-examples-references.sh. Do not edit manually.
| Example | Description | Workflow |
|---|---|---|
| EKS Upgrade Readiness 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 |
See CONTRIBUTING.md for how to add skills, steering workflows, and examples.
This repository provides sample code for educational and demonstration purposes only. It is not intended for direct production use without proper review, testing, and validation. Always test generated infrastructure artifacts (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.
This project is licensed under the MIT-0 License. See the LICENSE file.