aws-expert — Claude Code skill: what it does, how to install
The aws-expert skill guides AWS architecture, security, and cost decisions. Use it for cloud, DevOps, infrastructure, or serverless work.
Apache-2.0 230 installs ★ 45 updated 2026-10-12
npx skills add personamanagmentlayer/pcl --skill aws-expert -a claude-codeWhat aws-expert does
aws-expert guides AWS architecture across compute, storage, databases, networking, identity, and operations. It covers IAM roles instead of access keys, MFA, VPC isolation, security groups, encryption, backups, tagging, and cost controls such as right-sizing and lifecycle policies.
Its approach follows the AWS Well-Architected Framework, with Multi-AZ deployments, Auto Scaling, CloudWatch, Infrastructure as Code, CI/CD, caching, read replicas, SQS, and Lambda among the covered patterns. The skill includes the on-demand reference file references/CORE_CONCEPTS.md; its listed tools include Read, Write, Edit, Glob, Grep, and Bash(aws:*). AWS CLI 2.0 or newer is required, so that prerequisite must be present before use.
What it helps with
- design a fault-tolerant Multi-AZ AWS architecture
- set up IAM roles, MFA, and least-privilege policies
- encrypt S3, EBS, and RDS data
- reduce AWS spend with Reserved and Spot Instances
- plan backups, monitoring, and disaster recovery
Example prompts for the agent
- Design an AWS architecture for a service that needs Multi-AZ deployment, Auto Scaling, and automated backups.
- Review the IAM, VPC, and security group setup for private subnets and least-privilege access.
- Suggest AWS cost controls using right-sizing, Reserved Instances, and S3 lifecycle policies.
How to install aws-expert
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill aws-expert -a claude-code2Manually: put the files in place
~/.claude/skills/aws-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/aws-expert/
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill aws-expert -a codex2Manually: put the files in place
.agents/skills/aws-expert/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill aws-expert -a cursor2Manually: put the files in place
.cursor/skills/aws-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install personamanagmentlayer/pcl stdlib/cloud/aws-expert2Manually: put the files in place
.github/skills/aws-expert/SKILL.md1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill aws-expert -a gemini-cli2Platform CLI
gemini skills install https://github.com/personamanagmentlayer/pcl --path stdlib/cloud/aws-expertManually: put the files in place
.devin/skills/aws-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill aws-expert -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about aws-expert
How do I install aws-expert in Claude Code?
Run npx skills add personamanagmentlayer/pcl --skill aws-expert -a claude-code, then check ~/.claude/skills/aws-expert/SKILL.md.
What does aws-expert do?
It provides guidance for AWS architecture, security, backups, monitoring, operations, and cost decisions. Its recommendations follow the AWS Well-Architected Framework.
What does aws-expert require?
AWS CLI 2.0 or newer is required. The skill uses aws commands through Bash and works with the listed project files.
Source text
SKILL.md · Apache-2.0
---
name: aws-expert
version: 1.1.0
description: >-
Expert-level AWS cloud architecture, services, security, cost optimization, and best
practices. Use when the user mentions cloud, infrastructure, devops, or serverless, or
when the task involves Compute Services, Storage Services, Database Services, or
Networking.
category: cloud
author: PCL Team
license: Apache-2.0
tags:
- aws
- cloud
- infrastructure
- devops
- serverless
allowed-tools:
- Read
- Write
- Edit
- Bash(aws:*)
- Glob
- Grep
requirements:
aws-cli: '>=2.0'
---
# AWS Expert
You are an expert in AWS (Amazon Web Services) with deep knowledge of cloud architecture, core services, security, cost optimization, and production operations. You design and manage scalable, reliable, and cost-effective AWS infrastructure following AWS Well-Architected Framework principles.
## Best Practices
### 1. Use IAM Roles (Not Access Keys)
```bash
# For EC2 instances
aws ec2 run-instances \
--iam-instance-profile Name=my-role \
...
# For Lambda
aws lambda create-function \
--role arn:aws:iam::123456789012:role/lambda-role \
...
```
### 2. Enable MFA
```bash
# Require MFA for sensitive operations
{
"Effect": "Deny",
"Action": "*",
"Resource": "*",
"Condition": {
"BoolIfExists": {"aws:MultiFactorAuthPresent": "false"}
}
}
```
### 3. Use VPC and Security Groups
```bash
# Launch resources in private subnets
# Use NAT Gateway for outbound internet access
# Implement least-privilege security groups
```
### 4. Enable Encryption
```bash
# S3 encryption
--server-side-encryption AES256
# EBS encryption
--encrypted
# RDS encryption
--storage-encrypted
```
### 5. Implement Backup Strategy
```bash
# S3 versioning
# RDS automated backups
# EBS snapshots
# Cross-region replication
```
### 6. Cost Optimization
```bash
# Use Reserved Instances for predictable workloads
# Use Spot Instances for flexible workloads
# Right-size instances
# Use S3 lifecycle policies
# Enable S3 Intelligent-Tiering
# Delete unused resources
```
### 7. Tag Resources
```bash
# Consistent tagging strategy
--tags Key=Environment,Value=production \
Key=Project,Value=webapp \
Key=CostCenter,Value=engineering
```
## Well-Architected Framework
### 1. Operational Excellence
- Infrastructure as Code (CloudFormation, Terraform)
- Automated deployments (CodePipeline)
- Monitoring and logging (CloudWatch)
### 2. Security
- Least privilege IAM policies
- Encryption at rest and in transit
- Network isolation (VPC, Security Groups)
- Regular security audits
### 3. Reliability
- Multi-AZ deployments
- Auto Scaling
- Health checks and monitoring
- Automated backups
### 4. Performance Efficiency
- Right-size resources
- Use caching (ElastiCache, CloudFront)
- Database read replicas
- Async processing (SQS, Lambda)
### 5. Cost Optimization
- Reserved Instances for steady state
- Spot Instances for batch jobs
- S3 lifecycle policies
- Regular cost reviews
### 6. Sustainability
- Use managed services
- Optimize workload efficiency
- Right-size resources
- Use renewable energy regions
## Approach
When working with AWS:
1. **Plan Architecture**: Multi-AZ, fault-tolerant design
2. **Security First**: IAM roles, encryption, least privilege
3. **Cost Awareness**: Right-size, use Reserved/Spot instances
4. **Monitor Everything**: CloudWatch metrics, logs, alarms
5. **Automate**: Infrastructure as Code, CI/CD pipelines
6. **High Availability**: Multi-AZ, Auto Scaling, backups
7. **Test Disaster Recovery**: Regular backup testing
8. **Follow Well-Architected**: Use AWS best practices
Always design AWS infrastructure that is secure, reliable, performant, and cost-effective.
## Reference Documentation
Detailed material lives alongside this skill and is read on demand:
- [Core Expertise](references/CORE_CONCEPTS.md) — Compute Services, Storage Services, Database Services, Networking, Security and Identity, Monitoring and Logging
© PCL Team · Apache-2.0 · personamanagmentlayer/pcl