gcp

Manages Google Cloud architecture, IAM, Cloud Run, GKE, and cost operations via gcloud.

22|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/Lynricsy/HyperSkills --skill gcp-lynricsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcp
Source: https://github.com/Lynricsy/HyperSkills/tree/main/skills/gcp
Command: npx skills add https://github.com/Lynricsy/HyperSkills --skill gcp-lynricsy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Google Cloud's CLI defaults are frequently wrong for production (zonal Cloud SQL, us multi-region buckets, flat concurrency assumptions), IAM changes propagate unpredictably, and cost or incident investigations fail silently when flags like --freshness are missed. This Skill encodes verified defaults, safe deployment workflows, and audit procedures so agents operate Google Cloud correctly the first time. ## Core Features & Use Cases - Verified CLI discipline: 25 core rules checked against Google Cloud SDK 584.0.0, covering gcloud help validation, --quiet in headless runs, explicit --project scoping, and human-approval gates for IAM, delete, billing, and KMS operations. - Safe Cloud Run shipping: deploy with --no-traffic --tag, verify on the tag URL, shift 10% traffic, and roll back by revision, with correct handling of concurrency (80 x vCPU vs flat 80), timeout limits, and revision-immutable scaling flags. - IAM and storage audits: flag default service accounts with roles/editor, user-managed keys, missing deny policies, soft-delete billing, and lifecycle rules that raise costs instead of lowering them. - Use Case: Given a Cloud Run service YAML that saturates early and kills requests at five minutes, identify the 300s timeout default, the concurrency miscalculation, and ship the fix to 10% of traffic before full promotion. ## Quick Start Ask the agent to audit your Google Cloud project's IAM policy or review a Cloud Run service configuration for production readiness.

Frequently Asked Questions about gcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely deploy a Cloud Run service update?

Deploy with gcloud run deploy --no-traffic --tag=<tag>, verify the tagged URL directly, then shift traffic with gcloud run services update-traffic --to-tags=<tag>=10 before promoting to 100%. Rollback is instant via --to-revisions=<previous>=100 since revisions are immutable.

How do I audit a Google Cloud project's IAM policy?

Run gcloud projects get-iam-policy with policy version 3, flag basic roles, allUsers grants, default service accounts, and user-managed keys, then check deny and organization policies. Verify changes only after the 2-7 minute IAM propagation window.

What is the default Cloud Run concurrency limit?

Services created via the gcloud CLI or Terraform default to 80 times the number of vCPUs, while console-created services default to a flat 80, with a ceiling of 1000. The default applies only at service creation and is not re-derived on later deploys.

Why does gcloud logging read return no results for older incidents?

gcloud logging read defaults to --freshness=1d, so queries for events older than one day return empty and exit zero even with a timestamp filter. Always set --freshness explicitly wider than the incident window.

Does a Google Cloud budget stop spending when exceeded?

No, a Cloud Billing budget only sends alert notifications and never caps usage or spending. Use forecast-based thresholds for early warning, and enforce actual limits through quota reductions or scaling actions instead.

When should I use GKE instead of Cloud Run?

Default to Cloud Run for new work and choose GKE only when many interdependent services justify a shared scheduler, custom scheduling, operators, or GPU fleets. GKE Autopilot is the preferred path when a cluster is genuinely required.