convez.ai
MCP ServerDevOps & InfraestruturaIntermediário
aws-samples

APEX Skills — Platform Engineering com IA Agentiva

aws-samples/sample-apex-skills

Skills de engenharia de plataforma AWS para agentes de IA com conhecimento de especialistas

Ver no GitHub
BomPluginScore · de 0 a 100

Conjunto de skills especializadas para engenharia de plataforma em AWS, permitindo que agentes de IA (como Claude Code) acessem conhecimento de SSAs e especialistas. Comprime onboarding de meses para semanas através de instruções, scripts e recursos organizados seguindo o padrão Agent Skills aberto.

Instalação

$npx convez-ai aws-samples/sample-apex-skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
103
Forks
22
Acompanhando
1
Saúde
87%
Último commit
há 1 dia
Versão
v1.3.0
Issues abertas
62
Contribuidores
6

Casos de uso

  • Acelerar design e deployment de clusters EKS
  • Codificar melhores práticas de infraestrutura como conhecimento reutilizável
  • Estruturar workflows de engenharia com steering e checkpoints guiados
  • Automação de tarefas de platform engineering com agentes Claude Code

Veredito

Excelente repositório que democratiza conhecimento de engenharia de plataforma AWS através de skills estruturadas. Segue padrões abertos, integra bem com Claude Code e oferece tanto skills quanto steering/playbooks — ideal para times que querem escalar expertise.

README

A tradução para o português deste README ainda está na fila.

APEX Skills — Agentic Platform Engineering eXperience

Docs

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.


What's in This Repo

sample-apex-skills/
├── skills/       → 📚 Domain knowledge (platform-engineering best practices, Terraform, skill creation)
├── steering/     → 🎯 Guided workflows (optional — structured engagement playbooks)
├── examples/     → 🏗️ Hands-on exercises (deployable labs with planted issues)
└── misc/         → 🔧 Maintenance and tooling
    ├── evals/    → 🧪 5-layer skill evaluation framework (triggering, process, artifact, knowledge, quality)
    └── (scripts) → Sync skills from sources, update cross-references
DirectoryPurposeThink of it as...
skills/What the agent knows — reusable domain knowledgeAn expert's brain
steering/How the agent runs an engagement — slash commands, questionnaires, checkpoints, routingA senior SA's playbook
examples/How to try it — deploy, run APEX against it, see resultsA workshop lab
misc/Maintenance tooling and per-skill evaluation inputsThe toolbox

Key principle: Skills provide the knowledge. Steering provides the structure.


Quick Start

NPX Installer (recommended)

Prerequisites: Node.js 18+ and git must be installed.

npx apex-skills

Detects 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.0.0      # Pin to a specific release
npx apex-skills --branch feat/new-eks # Install from a branch
npx apex-skills --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 ~/.claude/commands
cp -r skills/* ~/.claude/skills/
ln -sfn "$(pwd)/steering/commands/apex" ~/.claude/commands/apex
ln -sfn "$(pwd)/steering" ~/.claude/apex-steering

Usage: 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?"

Kiro CLI

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/

Other Agent Harnesses

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.

Skills Reference

This table is auto-generated by misc/update-skills-references.sh. Do not edit manually.

SkillWhat It Covers
eks-best-practicesAdvisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning. Also answers Terraform configuration questions about terraform-aws-modules/terraform-aws-eks. Use for any EKS planning or architectural judgment call, even when phrased casually. Do NOT use for generating documents or code (eks-design, eks-build), scoring or auditing a live cluster (eks-operation-review, eks-upgrade-check), discovering what is running (eks-recon), MCP tooling setup (eks-mcp-server), or building developer platforms and IDPs (eks-platform-engineering).
eks-buildUse when building EKS clusters. Generates complete, production-ready Terraform projects with optional ArgoCD GitOps integration. Handles environment-specific constraints: air-gapped/VPC-endpoint-only networks, enterprise proxies, private container registries, compliance requirements. Supports 3 patterns: full Terraform, ArgoCD+Terraform, ArgoCD+ACK/KRO. Includes validated modules, two-phase webhook ordering, IRSA/Pod Identity, and 29+ addon configurations. Ask interactive questions or accept requirements YAML. Also use when (1) generating EKS Terraform code from scratch, (2) creating GitOps-managed EKS addons with ArgoCD, (3) scaffolding EKS projects with compliance constraints, (4) implementing two-phase webhook ordering for EKS addons, (5) configuring IRSA or Pod Identity for EKS workloads, (6) generating ArgoCD ApplicationSets for EKS addon management, or (7) comparing deployment patterns for implementation decisions.
eks-designUse when designing EKS architecture. Generates design documents with Mermaid diagrams, ADRs, security architecture, and validation reports. Translates requirements into tailored EKS designs guided by Well-Architected best practices. Covers cluster architecture, compute, networking, security, addons, observability, cost, and upgrade strategy. Also use when reviewing or validating existing EKS architectures, planning networking or security, evaluating deployment models, or generating architecture diagrams. Skip for short advisory recommendations without a formal document (eks-best-practices) and Internal Developer Platforms or progressive delivery (eks-platform-engineering).
eks-mcp-serverInstall, configure, and troubleshoot the EKS MCP Server connection in your AI assistant (Claude Code, Amazon Q CLI, Cursor). Use ONLY for MCP server setup problems — config file location (.mcp.json), IAM permissions for eks-mcp actions, uvx installation, choosing AWS-hosted vs self-hosted mode, or debugging why MCP tools fail to appear after config. Also activate if user mentions "eks mcp", "mcp server", "mcp.json", or "mcp tools not showing". Do NOT use for actual cluster operations once MCP is working — those go to eks-recon (discovery), eks-operation-review (audits), or eks-upgrade-check (upgrades).
eks-operation-reviewRun a structured EKS operational excellence assessment against a live cluster. Covers 10 areas — networking, autoscaling, observability, access & identity, add-ons, workload config, deployments, cluster lifecycle, IaC, operational processes — and produces a GREEN/AMBER/RED rated report with prioritized recommendations. Activate for any request to audit, review, health-check, or score an EKS cluster's operational posture, including section-scoped reviews of individual areas. Not for upgrade readiness, cluster discovery, or architectural design advice.
eks-platform-engineeringUse whenever someone is designing or building an Internal Developer Platform (IDP) or doing platform engineering on Amazon EKS — phrased as "build a developer platform", "self-service for developers", "golden paths", "IDP", or "set up Backstage / ArgoCD / Kargo". Covers the opinionated platform stack — developer portal (Backstage), GitOps delivery (ArgoCD, Argo Workflows), progressive delivery (Argo Rollouts canary with quality gates) and multi-stage promotion (Kargo), infrastructure abstraction (ACK, kro), application modeling (KubeVela/OAM), self-service provisioning, hub-and-spoke topology with the GitOps Bridge, identity/SSO (Keycloak, Pod Identity), measuring platform success (DORA, Apache DevLake), GenAI with Amazon Q Developer, and golden paths for AI/ML and data engineering. Trigger even if "platform engineering" is never said. Skip for single-cluster EKS architecture or cost/ops tuning with no platform angle (use eks-best-practices); for standalone Terraform use terraform-skill.
eks-reconEKS cluster reconnaissance and environment discovery. Detects compute strategy (Karpenter, MNG, Auto Mode, Fargate), IaC tooling (Terraform, CloudFormation, CDK, eksctl), CI/CD pipelines (GitHub Actions, GitLab, ArgoCD, Flux), add-on inventory, networking, security posture, and observability. Use this skill whenever someone asks about their EKS cluster, wants to understand their setup, is planning an upgrade or migration, needs cluster context for any reason, asks what version am I running, mentions wanting to review or document their cluster, or is about to make any EKS-related decision - even if they don't explicitly say reconnaissance or discovery. When in doubt about cluster state, run recon first. Skip for upgrade readiness scoring or deprecated API checks (eks-upgrade-check), operational audits with GREEN/AMBER/RED ratings (eks-operation-review), and architecture design documents or Mermaid diagrams (eks-design).
eks-upgrade-checkAssess EKS cluster upgrade readiness — run automated checks across 8 areas (version, breaking changes, deprecated APIs, add-on compatibility, node readiness, workload risks, AWS Insights, upgrade plan), calculate a 0-100 readiness score with a hard-blocker override, and generate a markdown/HTML report with prioritized remediation. Use this skill whenever someone asks "can I upgrade my cluster?", "is my cluster ready for 1.32?", "are we good to go to 1.33?", "what is blocking my upgrade?", or "should we move to the next version?" — even if they do not say "readiness" or "score". Falls back to AWS CLI and kubectl when the EKS MCP server is unavailable.
skill-creatorCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
steering-workflow-creatorAuthor a new steering workflow for any AWS service and pair it with a matching slash-command shim. Use when the user asks to create a steering workflow, add a workflow to apex, standardize steering, write a new workflow for EKS / RDS / Lambda / IAM / any AWS service, or build a phased playbook that plugs into a service hub. Covers the convention (frontmatter, header block, required sections), tool routing (knowledge vs. live MCP vs. setup-bridge), and the lint pass before handoff.
terraform-skillUse when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift, state corruption) with version-aware guards.
update-docsAudit and update every documentation surface in the APEX repo against the current state of skills, steering workflows, README marker tables, and the Docusaurus site under misc/website/. After any change to a skill (rename, retire, add, edit description), walk the repo, re-run script-managed surfaces if their --check fails, and reason through every tracked prose *.md to catch references that need updating. Use after adding/removing/renaming a skill, after editing SKILL.md frontmatter, after editing README marker blocks, or before publishing a docs change. Also use when the user says "update docs", "sync docs", "check docs", "run update-docs", or mentions that documentation might be stale.

Steering (Optional)

This table is auto-generated by misc/update-steering-references.sh. Do not edit manually.

Steering FileDescription
apexAPEX meta hub. Routes contributor requests about the repo itself — adding a new skill, authoring a new steering workflow, and other maintenance actions that are not tied to a specific AWS service.
eksEKS platform engineering hub. Routes to design, build, upgrade-readiness, and operational-review workflows. Use as the entry point for any EKS-related request.
designDay 0 architecture design workflow. 8-phase questionnaire for EKS cluster design, architecture reviews, and option comparisons.
eks-buildDay 1 infrastructure build workflow. Multi-phase questionnaire gathering requirements then generating production-ready Terraform code for EKS clusters.
eks-operation-reviewDay 2 operational-review workflow. Runs the eks-operation-review skill end-to-end — 10-section structured assessment of a live cluster's operational excellence, with GREEN/AMBER/RED ratings and a markdown/HTML report including prioritized actions and AWS reference links.
eks-platform-engineeringDay 1 platform-engineering workflow. Guides building an Internal Developer Platform on EKS — golden paths, developer portal (Backstage), GitOps and progressive delivery, self-service infrastructure (ACK/KRO), tenancy, AI/ML golden paths, and measuring success with DORA.
eks-upgrade-checkDay 2 upgrade-readiness assessment workflow. Runs the eks-upgrade-check skill end-to-end — 8 automated checks, 0-100 readiness score, markdown/HTML report with remediation steps.
new-skillMeta contributor workflow. Onboards a new skill end-to-end — scope intake, optional skill-creator drafting, sibling-graph survey, repo fan-out diff, and eval scaffold. Bimodal — greenfield authoring or retrofit on an existing skill that skipped the process.

Slash Commands (Claude Code)

CommandDescription
/apex:eksEKS platform engineering hub. Routes to design or upgrade workflows based on your request. Use for any EKS-related task -- architecture design, cluster upgrades, reviews, comparisons, or general EKS questions.
/apex:eks-buildBuild a production-ready EKS cluster. Multi-phase questionnaire gathering requirements then generating Terraform code via the eks-build skill.
/apex:eks-designDesign a new EKS cluster architecture. 8-phase questionnaire covering compute, networking, security, observability, cost, reliability, and multi-tenancy. Also handles architecture reviews and option comparisons.
/apex:eks-operation-reviewRun a structured EKS operational excellence assessment — 10-section review (cluster lifecycle, IaC/GitOps, access/identity, observability, workload config, networking, autoscaling, deployment practices, ops processes, add-on management) producing a rated report with GREEN/AMBER/RED findings and prioritized actions. Use when someone asks "run an EKS operational review", "audit my cluster", "EKS health check", "review my EKS posture", or asks for a section-scoped review (networking, RBAC, observability, etc.).
/apex:eks-platform-engineeringBuild an Internal Developer Platform on EKS — golden paths, developer portal (Backstage), GitOps and progressive delivery, self-service infrastructure (ACK/KRO), tenancy, AI/ML golden paths, and DORA-based measurement. Use to design or stand up developer self-service on EKS.
/apex:eks-upgrade-checkAssess EKS cluster upgrade readiness — automated checks across 8 areas (version, breaking changes, deprecated APIs, add-on compatibility, node readiness, workload risks, AWS Insights, upgrade plan), a 0-100 readiness score, and a markdown/HTML report with prioritized remediation. Use for upgrade-readiness assessments before running an actual upgrade.
/apex:new-skillOnboard a new skill end-to-end — draft it, survey siblings, fan out the repo edits, and scaffold the eval set. Bimodal — greenfield authoring or retrofit on an existing skill.

Steering files control how the agent runs an engagement — they don't contain domain knowledge (that's in skills), but define the interaction pattern. The hub (eks.md) is the entry point — it detects what the user wants and routes to the appropriate workflow. Each workflow follows a structured sequence with checkpoints and STOP gates. The commands/ directory provides agent-harness-specific entry points (e.g., Claude Code slash commands) that map to the hub and workflows.

The key test: If you removed all steering files, would the agent still know the right answers? Yes — skills provide the knowledge. But the agent wouldn't know how to run the engagement.


Examples

This table is auto-generated by misc/update-examples-references.sh. Do not edit manually.

ExampleDescriptionWorkflow
EKS Upgrade Readiness CheckDeploy 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

Contributing

See CONTRIBUTING.md for guidelines on:

  • Where new content goes (skills vs steering vs examples)
  • How to create a new skill
  • How to create a new steering workflow
  • How to create a new example
  • How to add evals for a new skill

Sources

All best practices content is sourced from public AWS documentation:


License

This project is licensed under the MIT-0 License. See the LICENSE file.

Ver o original no GitHub

Bom para

Relacionados