Use 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…
Execute a workload migration from x86 (amd64) to AWS Graviton (arm64) — set up the Arm migration MCP server for code, dependency, and container arm64-readiness scanning, then run the migration — pre-migration scanning, Karpenter arm64 node cutover, and multi-arch CI pipelines. Use when someone says "migrate to…
Create 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.
Use 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.
Audit 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…
Deterministic AWS Well-Architected Framework review of an Amazon EKS cluster (Linux nodes only). Unofficial — not the AWS Well-Architected Tool, no official EKS lens exists, and it maps to no compliance framework (CIS, PCI or otherwise). Collects live data via kubectl and aws, scores it across five of the six pillars…
APEX router for Amazon EKS and Amazon ECS work. Use it first for any EKS, ECS or APEX skills request, even one that names a single skill or that another APEX skill's description also matches: once loaded, it decides the route. Reads the request and workspace, asks only what the route still needs, infers the customer's…
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Coding teammate — writes production code and tests from specs and task definitions. Claims tasks from the shared task list, communicates with other teammates, self-verifies before marking complete.
DevOps teammate — infrastructure, CI/CD, containers, configuration, and documentation. Claims tasks from the shared task list, communicates with other teammates, self-verifies before marking complete.
Lead role assumed by the main agent — researches, designs, specs, and plans, emits a Handoff Package (spawn plan + task queue), then drives the build-review loop from it. If spawned as a subagent instead, plans only and returns the Handoff Package for the main agent to execute.
Code review teammate — analyzes implementations for correctness, security, and maintainability. Communicates directly with implementers for clarifications. Writes structured findings to review.md.
Audits and optimizes the entire /.claude configuration — settings, agents, rules, skills, plugins, and MCP servers — for the current Claude model and latest Claude Code features.
Write product code that fetches from external APIs concurrently and caches every response to disk, instead of looping calls one-at-a-time with no reuse. Use this skill WHENEVER you are writing or refactoring code that makes more than a handful of independent network calls — REST/HTTP APIs, terminology or lookup…
Technical writing patterns for READMEs, runbooks, and architecture docs, with accuracy verification. Use when writing documentation, creating runbooks, or documenting system architecture.
Conventional commit style, branch naming, and merge-conflict resolution, with commit-commands plugin and gh CLI integration. Use when working with version control, creating branches, writing commits, or resolving merge conflicts.
Spec-driven development loop with parallel task groups and the .claude/specs/ / structure (spec.md, design.md, tasks.md, review.md). Use before any non-trivial work that touches multiple files, involves architectural choices, or will be delegated to an agent team.
Lighter code-review teammate for low-risk scopes — mechanical changes (headers, formatting, version/lockfile bumps, renames, regenerated files), docs-only work, and narrow fix-verification cycles. Same authority and output contract as review-agent, at lower effort. The lead picks it per scope; anything touching IAM…
Evaluates AWS Health event and AWS Security Hub finding impact on application workloads using topology knowledge. Determines blast radius, affected teams, and notification routing. Use this skill when investigating incidents triggered by AWS Health events (scheduled maintenance, operational issues, service…
Final integration build and test verification. Validates that implemented code compiles, passes all test suites, and meets quality gates before deployment.
★not rated 66 3mo agoA31 tokens
MIT-0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: