From gcp-cloud
Choose GCP compute by operational burden: Cloud Run (default for stateless containers/HTTP, scale-to-zero), GKE/Autopilot (k8s/portability), Cloud Functions (small event handlers), GCE (legacy); design Pub/Sub integration with idempotency + dead-letter topics.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gcp-cloud:gcp-compute-selectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Workload | Compute |
| Workload | Compute |
|---|---|
| Stateless container / HTTP (most services) | Cloud Run (default) |
| Need k8s / portability | GKE (Autopilot to cut ops) |
| Small event handler | Cloud Functions |
| Legacy / specific OS | GCE |
Cloud Run is the right default; reach for GKE only when k8s genuinely earns it.
Pub/Sub to decouple; consumers idempotent + dead-letter topic. No hand-rolled queues.
npx claudepluginhub mcorbett51090/ravenclaude --plugin gcp-cloudGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.