Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
AWSSkillaws/aws-sdk-net/.agents/skills/aws-sdk-net-devconfig/SKILL.md
Use when creating, validating, or reasoning about DevConfig files for AWS SDK for .NET changes, including deciding whether Core or Services entries are required, choosing patch vs minor bumps, and writing changelog messages.
AWSSkillaws/aws-sdk-net/.agents/skills/aws-sdk-net-maintainer/SKILL.md
Use when working on the AWS SDK for .NET source code itself, including Core runtime changes, service client implementations, generator or model changes, repo-specific build and validation flows, and V3/V4 branch-targeting decisions.
AWSSkillaws/aws-sdk-net/.claude/skills/verify-smithy-service-parity/SKILL.md
Use when validating that a C2J-to-Smithy migrated AWS SDK service builds, packages, and stays API-compatible with the shipping SDK, or before reporting such a migration as done, verified, clean, or unblocked.
AWSSkillaws/tools-for-devops-agent/skills/agentcore-observability-setup/SKILL.md
Validates and bootstraps Amazon Bedrock AgentCore observability so customers can trace
AWSSkillaws/tools-for-devops-agent/skills/agentcore-ops-review/SKILL.md
Comprehensive operational review procedures for Amazon Bedrock
AWSSkillaws/tools-for-devops-agent/skills/aiml-access-diagnostics/SKILL.md
Use this skill when diagnosing IAM and access failures for Bedrock and SageMaker. It traces the authorization chain — caller identity, iam:PassRole, trust policy, role permissions, resource policies, SCPs — to name the denying hop and propose a scoped policy. Read-only.
AWSSkillaws/tools-for-devops-agent/skills/aiml-gpu-training-cluster-investigation/SKILL.md
Use this skill for GPU training or inference clusters on SageMaker HyperPod (Slurm or
AWSSkillaws/tools-for-devops-agent/skills/analytics-opensearch-expertise/SKILL.md
Amazon OpenSearch Service domain health assessment. Performs read-only, API-driven checks against a customer's OpenSearch domain(s) covering cluster health, node/shard configuration, performance metrics, security posture, and cost optimization signals. Activate this skill for requests about OpenSearch or Elasticsearch domain health, cluster review, domain assessment, performance, security posture, or cost optimization. Given a domain ARN (or name + region), it produces a structured findings report with prioritized recommendations. All checks use read-only AWS control-plane APIs (es:Describe*, es:GetCompatibleVersions, es:DescribeReservedInstances, cloudwatch:GetMetricData) — no data-plane access required.
AWSSkillaws/tools-for-devops-agent/skills/aws-backup-coverage-review/SKILL.md
AWS Backup coverage and data protection posture review. Determines
AWSSkillaws/tools-for-devops-agent/skills/aws-eks-healthdashboard/SKILL.md
Use this skill when the user wants to know whether an Amazon EKS cluster is healthy right now, or asks you to assess, triage, or report on the state of an EKS cluster, its control plane, or its nodes — even when they don't say \"dashboard\" or name a specific subsystem. It produces a read-only, point-in-time health snapshot grading control-plane signals (etcd, API Priority & Fairness, API-server latency and errors, scheduler) and node/data-plane signals (node conditions, utilization, EC2/ENA/EBS, NAT, CoreDNS, Karpenter, nodegroup registration), from whatever observability is connected (CloudWatch, native EKS metrics, Prometheus, Datadog, New Relic, Dynatrace, or Splunk). Reach for it for \"is my cluster okay\" questions, control-plane or node-health checks, and latency/throttling spikes; it only reads state and does not remediate. This is a current-state snapshot, not a best-practices audit — for a full EKS Best Practices operational review use aws-eks-operations-review instead.
AWSSkillaws/tools-for-devops-agent/skills/aws-eks-operations-review/SKILL.md
Use this skill when someone wants an Amazon EKS cluster graded against best practices. Use it when they ask to review, assess, audit, or grade a cluster; ask for an operations review, security review, operational-readiness or pre-upgrade check, inventory, or CWR; ask whether a cluster is production-ready or safe to upgrade; ask what risks, gaps, or misconfigurations it carries; or describe Kubernetes workloads on AWS without naming EKS. It grades nine pillars — Operations, Resilience, Security, Scalability, Performance, Observability, Networking, Cost, Control Plane — plus AWS API and Cluster Insights, and returns evidence-backed PASS/FAIL/N/A scorecards with prioritized remediations. Do not use it for a quick ungraded health snapshot or an active incident investigation.
AWSSkillaws/tools-for-devops-agent/skills/aws-fsxn-operations-review/SKILL.md
Amazon FSx for NetApp ONTAP Operational Review. Use when a user asks to review, audit, assess, or health-check FSx for NetApp ONTAP (FSxN / FSx ONTAP) — a file system, SVM, volume, or the whole footprint — for best-practices posture across Backup, Observability, Operations, Performance, and Security, in production or pre-production. Activate even on a brief request with no file-system IDs: the skill self-discovers all ONTAP file systems in the account/region and runs all pillars by default, so a bare account+region (or no scope) is enough — do not wait for named resources. Strictly read-only and fully automated via public AWS APIs (fsx, cloudwatch, backup, ec2); no manual steps, no ONTAP CLI. Triggers: "FSxN operational review", "FSx ONTAP review", "review my FSxN", "audit my FSx ONTAP", "check my FSxN posture", "FSx ONTAP best-practices audit", "FSxN health check", "assess my ONTAP file system".
AWSSkillaws/tools-for-devops-agent/skills/aws-health-events/SKILL.md
ALWAYS use this skill in the beginning of any incident investigation, root cause
AWSSkillaws/tools-for-devops-agent/skills/aws-natgw-traffic-analysis/SKILL.md
Use this skill when a user wants to understand what traffic is going through an AWS NAT Gateway, why it takes that path, or how to reduce NAT Gateway cost - for example "why is my NAT Gateway bill so high", "what is going through my NAT Gateway", traffic leaving through NAT instead of over peering or a VPC endpoint, EKS, ECS, or other private-subnet workloads sending heavy AWS API, container image, or S3 traffic through NAT, S3 traffic still hitting NAT even though a Gateway Endpoint exists, whether Gateway or Interface Endpoints are actually being used, customer-owned or BYOIP public IPs appearing as NAT destinations, estimating how much fixing NAT traffic would save, which flow logs to use for NAT analysis, or before recommending a Cross-Region S3 Interface Endpoint. Also use it when the user shares or points to NAT Gateway VPC Flow Logs, or asks which resource or service is behind a NAT Gateway destination IP. Read-only and advisory: reports traffic in GB and percent and never changes resources.
AWSSkillaws/tools-for-devops-agent/skills/aws-routing/SKILL.md
Use this skill when the user wants to know which path AWS will pick for their traffic, why traffic took an unexpected route, or how to make AWS prefer a path. Covers Cloud WAN CNE route evaluation, Direct Connect Gateway local vs remote region preference, Transit Gateway route tables, ECMP and peering, VPC longest-prefix-match, BGP traffic engineering (LP communities 7224:7100/7200/7300, AS-path prepending, MED), DX + VPN redundancy and failover, and asymmetric routing. Use it even when the user only describes a symptom, such as "traffic is leaving the region", "not using my local Direct Connect", "routing to the wrong VIF/location", or "path is asymmetric". Read-only: analysis, recommendations, and describe/get/list validation commands grounded in public AWS docs.
AWSSkillaws/tools-for-devops-agent/skills/aws-vpc-dns-investigation/SKILL.md
Use this skill when a name is not resolving as expected inside a VPC, or before applying a DNS control-plane change. Activate on symptoms such as NXDOMAIN or SERVFAIL from an EC2 instance, a hostname resolving to a public address when a private endpoint was expected, an AWS service endpoint that stopped resolving after a VPC endpoint or Route 53 change, an application reaching the wrong IP, resolution that works from one instance but not another, IPv6 or dualstack resolution differences, a suspected on-premises forwarding or hybrid DNS problem, or a request to check whether enabling private DNS, adding a Resolver rule, associating a private hosted zone, attaching DNS Firewall, or associating a Route 53 Profile would break anything. It drives the aws-vpc-dns-diagnostics MCP server to observe live resolution from inside the subnet and to simulate a proposed change before it is applied.
AWSSkillaws/tools-for-devops-agent/skills/bedrock-adoption-readiness/SKILL.md
Amazon Bedrock production readiness assessment covering IAM governance, data retention (ZDR), quota and capacity headroom, and operational observability across Standard Bedrock and Mantle surfaces. Use this skill when a user asks to review Bedrock readiness, assess Bedrock security posture, evaluate quota headroom, check ZDR configuration, validate Bedrock operational setup, or prepare for Bedrock production deployment. Triggers on "Bedrock readiness review", "am I ready for Bedrock production", "Bedrock security assessment", "check my Bedrock quotas", "Bedrock adoption audit", "Bedrock operational review", or "assess my Bedrock environment".
AWSSkillaws/tools-for-devops-agent/skills/bedrock-operation-review/SKILL.md
Comprehensive Amazon Bedrock review aligned with the AWS
AWSSkillaws/tools-for-devops-agent/skills/bronto-dataset-discovery/SKILL.md
Load this skill when investigating an incident or answering a question that needs logs from Bronto and the dataset that holds them is not already known - for example a service, host, function or resource that is failing, slow or throwing errors. It finds which Bronto datasets hold that service's logs, which key identifies the service, and whether there is data in the incident window, before any log search runs.
AWSSkillaws/tools-for-devops-agent/skills/bronto-error-investigation/SKILL.md
Load this skill when an investigation needs to explain errors in logs held in Bronto - an error surge, a failing service, a specific error event or a Bronto monitor alert. It isolates the error, finds when it started, breaks it down by version, host, customer, endpoint, client and region to find what it is concentrated on, verifies the suspect against a control query, and reports the scope, a hypothesis and next steps with links to the supporting searches.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
