claudeskills.page

21 skills · category

Cloud Platforms skills for Claude Code

Skills for the platforms apps actually ship to: AWS Lambda, IAM and CDK, S3 and R2, Google Cloud Run, Azure Functions, Cloudflare Workers, Vercel, Fly.io, Supabase and Firebase, plus a cost audit that finds the spend nobody is watching.

Download all 21 (.zip) Browse the list
  1. 171AWS CDK
  2. 172AWS CloudFront
  3. 173AWS ECS on Fargate
  4. 174AWS IAM Least Privilege
  5. 175AWS Lambda
  6. 176AWS Messaging
  7. 177AWS RDS and Aurora
  8. 178Azure Container Apps
  9. 179Azure Functions
  10. 180Cloud Cost Audit
  11. 181Google Cloud Run
  12. 182Cloudflare Workers
  13. 183Firebase Backend
  14. 184Fly.io Apps
  15. 185Google BigQuery
  16. 186Netlify Deploys
  17. 187PaaS Deploys
  18. 188S3 and R2 Object Storage
  19. 189Supabase Backend
  20. 190Vercel Deploys
  21. 191VPS Deployment

Every cloud platforms skill

Each card opens the full playbook, example prompts and install commands.

No. 171

AWS CDK

CDK diffs you can trust before you hit deploy

Claude structures CDK apps into explicit-environment stateful and stateless stacks, uses L2 grant methods instead of hand-written policies, and reads every cdk diff for replacements before deploy. It keeps logical IDs stable through refactors, untangles cross-stack export deadlocks, and adds assertion tests and cdk-nag so encryption and retention regressions fail CI.

aws-cdk 194 lines
No. 172

AWS CloudFront

Private origins, small cache keys, high hit ratios

Claude puts S3 behind Origin Access Control with the bucket fully private, splits traffic into per-path behaviors, and keeps cache keys limited to what changes the response while forwarding the rest through origin request policies. Assets get long immutable TTLs, HTML stays fresh, edge logic starts with CloudFront Functions, and every change is verified with x-cache headers and hit-ratio metrics.

aws-cloudfront 236 lines
No. 173

AWS ECS on Fargate

Containers that deploy, drain and roll back cleanly

Claude writes task definitions with valid Fargate sizes, separate execution and task roles, secrets pulled by reference and logs that cannot block the app. Services run in private subnets with the endpoints they need, deploy with a circuit breaker or native blue/green and canary strategies, drain on SIGTERM, and scale on request count or queue backlog instead of guesses.

aws-ecs-fargate 251 lines
★ No. 174

AWS IAM Least Privilege

Exact permissions, and AccessDenied solved by evidence

Claude maps each API call to the exact IAM actions, ARNs and condition keys it needs instead of reaching for wildcards. AccessDenied errors are traced through caller identity, CloudTrail, decoded messages and the evaluation order to the policy type that denied. Policies are validated with Access Analyzer and a bundled stdlib linter that flags PassRole, escalation paths and open OIDC trusts.

aws-iam 204 lines · 2 files
No. 175

AWS Lambda

Fast cold starts, safe retries, no silent drops

Claude writes Lambda handlers that create clients once at init, stay well inside timeouts, and return partial batch failures so one bad SQS message does not replay the rest. It measures Init Duration before tuning, chooses between bundling, arm64, SnapStart and provisioned concurrency, and makes sure every async trigger has a failure destination and alarms.

aws-lambda 184 lines · 2 files
No. 176

AWS Messaging

Queues, topics and buses that survive duplicates

Claude picks between SQS, SNS fan-out, EventBridge rules, Pipes and Scheduler based on ordering, routing and consumer count, then configures visibility timeouts, long polling and DLQs with alarms. Consumers are written idempotently with partial batch failure reporting, and the poison message, duplicate and redrive paths are tested before anything ships.

aws-messaging 221 lines
No. 177

AWS RDS and Aurora

Right engine, tested failover, no surprise I/O bill

Guides Claude through running PostgreSQL and MySQL on AWS from measured load: choosing RDS, Aurora, or Serverless v2, sizing for the working set, testing failover, and keeping settings in custom parameter groups. It plans major upgrades as blue/green deployments with the logical-replication and PITR caveats, reduces RDS Proxy pinning, and runs a script that compares Aurora Standard and I/O-Optimized from your bill.

aws-rds-aurora 285 lines · 2 files
No. 178

Azure Container Apps

Revisions, KEDA scaling and secrets without passwords

Claude defines Container Apps in YAML or Bicep with managed identity for ACR and Key Vault, real startup and readiness probes, and ingress limited to what is needed. Scaling uses HTTP or KEDA queue rules tuned per workload, releases run as revisions with explicit traffic weights and labels, and debugging starts from system logs instead of guesswork.

azure-container-apps 255 lines
No. 179

Azure Functions

Current models, managed identity and handled poison queues

Claude builds function apps on the current programming model for each language, migrating off in-process .NET and function.json-era code before the support cutoff. It picks a hosting plan from latency and networking needs, connects triggers through managed identity and Key Vault references, tunes host.json per trigger, and makes sure failing messages land in a monitored poison or dead-letter queue.

azure-functions 204 lines
No. 180

Cloud Cost Audit

Find the money, prove it, cut it with sign-off

Claude breaks the bill down by service, usage type and tag, explains the handful of items that make up most of the spend, and hunts idle disks, unused IPs, log groups without retention and NAT traffic that a gateway endpoint would remove. It rightsizes before recommending commitments, never deletes without approval, and delivers a savings report with evidence for every number.

cloud-cost-audit 169 lines · 3 files
No. 181

Google Cloud Run

Containers tuned for concurrency, cost and calm rollouts

Claude prepares containers that honor the Cloud Run contract, then picks concurrency, CPU allocation and instance limits from how the app actually behaves instead of defaults. Services run as dedicated service accounts with Secret Manager secrets, new revisions deploy with no traffic behind a tag, and traffic shifts in steps with an exact rollback command ready.

cloud-run 161 lines
No. 182

Cloudflare Workers

Right storage per binding, typed env, one-command rollback

Claude configures Workers with explicit compatibility dates, generated binding types and per-environment bindings, then picks KV, D1, R2, Durable Objects or Queues from the access pattern rather than habit. Code stays inside CPU and memory limits, tests run in the real Workers runtime via Vitest, and releases go out as versions with traffic splitting and a known rollback.

cloudflare-workers 203 lines
No. 183

Firebase Backend

Query-shaped Firestore models guarded by tested rules

Claude models Firestore collections from the app's actual queries, avoiding hotspots and unbounded documents, and writes Security Rules that check ownership, roles and the exact shape of every write. Rules are proven with allowed and denied cases on the Emulator Suite before deploy, and 2nd gen Cloud Functions dedupe retried events and keep privileged fields out of client reach.

firebase-backend 209 lines · 2 files
No. 184

Fly.io Apps

Machines, volumes and regions configured on purpose

Claude writes fly.toml with real health checks, request concurrency limits and deliberate auto stop settings, runs at least two Machines for anything that must stay up, and explains that each volume lives on one host and needs its own backups. Migrations run as release commands that are safe during rolling deploys, and rollback is a redeploy of a recorded image.

fly-io 193 lines
No. 185

Google BigQuery

Scan less, pay less, know who spent what

Claude starts a BigQuery task by finding the real cost drivers in INFORMATION_SCHEMA, then fixes table design with partitioning, clustering and required partition filters, rewrites the worst queries and proves the savings with dry runs. It adds byte caps and daily quotas, compares on-demand with editions using measured slot-hours, and grants access through datasets, authorized views and row policies.

gcp-bigquery 235 lines · 2 files
No. 186

Netlify Deploys

Builds, redirects and functions that behave per context

Claude moves Netlify configuration into netlify.toml with pinned Node versions, monorepo base directories and ignore commands, then scopes environment variables per deploy context. Redirects are ordered with shadowing and force understood, assets get immutable caching, functions and forms follow current limits, and every change is checked on a deploy preview with a one-step rollback ready.

netlify-deploys 265 lines
No. 187

PaaS Deploys

Render, Railway or Heroku, configured from the repo

Claude picks the platform that fits the stack, then writes render.yaml, railway.json or a Procfile so services, databases and variables live in the repo. Apps bind to $PORT with real health checks, migrations run once in the release phase and stay backward compatible, database pools fit plan limits, and the free-tier traps such as sleeping instances and expiring databases are called out early.

paas-deploys 235 lines
No. 188

S3 and R2 Object Storage

Private buckets, presigned uploads, no surprise bills

Claude keeps buckets private with Block Public Access and ACLs disabled, then serves files through short-lived presigned URLs or CloudFront with origin access control. Uploads go straight from the browser with server-chosen keys and enforced size limits, large files use multipart with exposed ETags, and lifecycle rules abort stale uploads and expire old versions on S3 or R2.

s3-object-storage 183 lines
No. 189

Supabase Backend

Treat the database as the security boundary it is

Claude builds Supabase projects with the CLI and versioned migrations, enables RLS on every exposed table with per-operation policies that are indexed and tested as two different users, and keeps the secret key off clients. Server auth uses @supabase/ssr with verified users, storage paths are scoped by user folder, and types are regenerated after each schema change.

supabase-backend 204 lines
No. 190

Vercel Deploys

Reproducible builds, scoped env vars, instant rollback

Claude reproduces Vercel builds locally with vercel pull and vercel build before guessing, scopes env vars per Production, Preview and branch, and remembers that changes need a redeploy. Functions run on the Node.js runtime near the database with sensible maxDuration, previews stay protected, monorepo builds skip unaffected apps, and production moves by promotion with a known rollback.

vercel-deploys 158 lines
★ No. 191

VPS Deployment

One server, done properly: TLS, backups, no-drop deploys

Claude sets up a VPS the way an experienced operator would: key-only SSH, a firewall that Docker cannot bypass, Compose services on internal networks behind Caddy with automatic TLS, and a deploy script that starts a healthy replica before draining the old one. Nightly restic and pg_dump backups go off-site with a restore test, and exposure is verified from outside the server.

vps-deployment 272 lines · 2 files

Choosing Cloud Platforms skills

Install the skills that match requests you make every week; each costs about 100 tokens of standing context until it loads. If you are not sure where to begin, start with AWS IAM Least Privilege and VPS Deployment. For background, read The Best Claude Code Skills in 2026, by Use Case, How to Install Claude Code Skills (5 Ways) and Personal vs Project Skills.

By technology: AWS skillsCloudflare skillsJavaScript skillsPostgreSQL skillsGoogle Cloud skillsNode.js skillsMicrosoft Azure skills

Install several

Install several at once

The installer accepts any number of skill names. Add --project to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- aws-cdk aws-cloudfront aws-ecs-fargate aws-iam aws-lambda aws-messaging aws-rds-aurora azure-container-apps azure-functions cloud-cost-audit cloud-run cloudflare-workers firebase-backend fly-io gcp-bigquery netlify-deploys paas-deploys s3-object-storage supabase-backend vercel-deploys vps-deployment

Cloud Platforms skills FAQ

How do I install every Cloud Platforms skill at once?

Download the bundle at https://claudeskills.page/downloads/category/cloud.zip and unzip it into ~/.claude/skills/ (or .claude/skills/ inside a repository). To pick a few, pass several names to the installer: curl -fsSL https://claudeskills.page/install.sh | sh -s -- aws-cdk aws-cloudfront aws-ecs-fargate.

Will installing 21 skills slow Claude Code down?

No. Claude Code keeps only each skill's short description in context — roughly 100 tokens per skill — and loads the full instructions only when a request matches. Install the whole category if it fits your work; unused skills cost almost nothing.

Which Cloud Platforms skill should I start with?

Start with AWS IAM Least Privilege, VPS Deployment. They cover the most common requests in this category; add the rest as your work calls for them.

Featured in Data Engineering Stack.

Explore other categories

esc