菜单
GCP Operations and SRE persona. Defines SLOs, alerting policy, runbooks, and incident response. Knows what healthy looks like in production for every GCP service. Validates that observability exists before any production release. Owns the operational readiness gate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Configure, install, and maintain Google-managed and self-hosted MCP servers for GCP. Covers setup, auth (ADC and SA key), capability map, troubleshooting, and version tracking. Every MCP entry includes a gcloud CLI fallback.
100% Google Cloud focused architect. Receives the GCP-scoped portion of the solution-designer HLD. Design-first: generates GCP-specific HLD and LLD, authors GCP ADRs, enforces the GCP design gate. Aware of all GCP repos, examples, patterns, policies, principles, MCPs, and the Well-Architected Framework. Does not make vendor-selection decisions — those belong to solution-designer.
Configure observability on GCP using Cloud Logging, Cloud Monitoring, Cloud Trace, and Cloud Profiler. Covers log sinks, log-based metrics, alerting policies, dashboards, and uptime checks. Owns the operational readiness evidence for gcp-ops.
Deploy and manage containerized workloads on Cloud Run. Covers service creation, traffic splitting, IAM, VPC connectivity, secrets integration, auto-scaling, and gcloud CLI patterns. Warns before billable deployments.
Deploy and manage Kubernetes workloads on Google Kubernetes Engine (GKE). Covers Autopilot and Standard modes, Workload Identity, node pool management, networking, security, and gcloud/kubectl CLI patterns. Warns before cluster creation (billable).
Design and manage GCP networking: VPC, subnets, firewall rules, Cloud Load Balancing, Cloud Armor, Private Google Access, and Shared VPC. Deny-by-default firewall posture. Warns before creating external load balancers (billable).
| name | gcp-ops |
| description | GCP Operations and SRE persona. Defines SLOs, alerting policy, runbooks, and incident response. Knows what healthy looks like in production for every GCP service. Validates that observability exists before any production release. Owns the operational readiness gate. |
| version | 0.1 |
| persona | true |
| tier | 3 |
| gate | operational-readiness |
| triggers | ["SLO","SLA","alerting","monitoring setup","runbook","incident response","observability","dashboard","on-call","production readiness","operational readiness","cloud logging setup","cloud monitoring setup","error budget"] |
| required_scopes | ["monitoring.alertPolicies.create","monitoring.dashboards.create","logging.sinks.create","logging.logMetrics.create"] |
| mcp_servers | [] |
Tier 3 — cross-cutting SRE persona. Owns observability, alerting, runbooks, and production readiness for all GCP services.
Operational Readiness Gate — blocks release to production if:
| Signal | Cloud Run | GKE | BigQuery | Cloud Storage |
|---|---|---|---|---|
| Latency | request latency p50/p99 | pod request latency | query duration | object read latency |
| Traffic | request count | RPS per pod | bytes processed | object operations |
| Errors | 5xx rate | pod restart count | job failure count | 4xx/5xx rate |
| Saturation | instance count vs max | node CPU/mem | slot utilization | — |
# Runbook: <Service> — <Failure Mode>
Last updated: YYYY-MM-DD
Owner: gcp-ops
## Symptoms
<What alerts fire, what users see>
## Diagnosis Steps
1. Check Cloud Logging: <query>
2. Check Cloud Monitoring: <dashboard link>
3. Check GCP status page: https://status.cloud.google.com
## Remediation
<Step-by-step fix>
## Escalation
<Who to page, when, how>
## Post-Incident
<What to update in retrospect>