ericrisco/rsc-harness / skills/aws-essentials
aws-essentials
VerifiedUse when standing up the core AWS surface a small product needs: hardening a fresh account, a private S3 bucket, encrypted RDS Postgres, ECS Fargate vs EC2, CloudFront + OAC, or scoping an IAM policy to least privilege. NOT the CI pipeline that ships the container (that is `deployment`), NOT app-code access-control review (that is `security-audit`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| evals/README.md | markdown | 747 B |
| evals/cases.yaml | config | 2.9 KB |
| references/iam-least-privilege.md | markdown | 4.8 KB |
| references/rds-cloudfront-recipes.md | markdown | 4.7 KB |
| scripts/verify.shexecutable | script | 4.5 KB |
evals/cases.yaml
View on GitHubskill: aws-essentials
should_trigger:
- prompt: "Set up an S3 bucket for user profile uploads on AWS"
why: Core S3 provisioning — the bucket-defaults + presigned-URL path this skill owns.
- prompt: "This IAM role has AdministratorAccess, tighten it to least privilege"
why: Cloud IAM scoping. Non-obvious that this is aws-essentials and not security-audit — it is the cloud-identity surface, not app-code access control.
- prompt: "Spin up an encrypted Postgres on RDS with Multi-AZ"
why: RDS provisioning, including the encrypt-at-create gotcha this skill warns about.
- prompt: "monta CloudFront delante del meu bucket S3 privat"
why: Catalan phrasing for the CloudFront+OAC-over-private-S3 recipe.
- prompt: "Should my container run on ECS Fargate or EC2 for a low-traffic app?"
why: Compute decision. Non-obvious — the word AWS never appears, but ECS implies it and the Fargate-vs-EC2 tradeoff is core here.
- prompt: "My S3 bucket is public and I don't know why — make it private and still serve the images"
why: Symptom phrasing; routes to keeping Block Public Access on + CloudFront/OAC instead of public-read.
- prompt: "Lock down the security group on our RDS instance, it's open to the world"
why: DB-SG-references-app-SG hardening, a named anti-pattern in this skill.
should_not_trigger:
- prompt: "Write the Dockerfile and GitHub Actions workflow to deploy to ECS"
route_to: deployment
why: Containerization + CI pipeline (incl. OIDC to ECR), not infra provisioning. This skill ends where the container starts shipping.
- prompt: "Review this login handler for broken access control"
route_to: security-audit
why: App-code OWASP review, not cloud IAM least-privilege.
- prompt: "Model a single-table DynamoDB schema for my app"
route_to: dynamodb
why: NoSQL data modeling, not the AWS core-setup surface (this skill picks RDS for relational and points at dynamodb otherwise).
- prompt: "Optimize this slow Postgres query and add the right indexes"
route_to: postgresdb
why: Query/schema tuning on an existing DB, not RDS provisioning.
- prompt: "Set up Cloudflare Workers and a CDN for my static site"
route_to: cloudflare
why: Different provider's edge/CDN, not AWS CloudFront.
capability:
- scenario: "Provision storage and a CDN for a small product's user-uploaded images on AWS, with least privilege and no shortcuts."
must_include:
- Private S3 bucket with Block Public Access kept ON (no public-read ACL, no re-enabled ACLs).
- Access via IAM/bucket policy + presigned URLs or CloudFront — never a public bucket.
- CloudFront uses OAC (not the legacy OAI) and serves over HTTPS.
- IAM policy scoped to the specific bucket ARN + specific actions (no "Action":"*" on "Resource":"*").
- No long-lived access keys — a task role / temporary credentials instead.
- Acknowledges encryption at rest (SSE-S3 default on the bucket).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |