gcp-ops
Skill4 starsChanged 4 months agoMITView on GitHub
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. Use when the user mentions: SLA, monitoring setup, dashboard, on-call, production readiness, cloud logging setup, cloud monitoring setup, error budget. Use this for SLO targets, runbooks and release gating; use logging-monitoring instead to configure the underlying Cloud Logging and Monitoring resources.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-architectSkill
- bigquerySkill
- cloud-runSkill
- cloud-storageSkill
- gcloud-guardrailsSkill
- gcp-architectSkill
- gcp-project-contextSkill
- gcp-qaSkill
- gcp-securitySkill
- gkeSkill
- google-skills-catalogSkill
- iamSkill
- logging-monitoringSkill
- mcp-serversSkill
- networkingSkill
- solution-designerSkill
- terraform-gcpSkill
- vertex-aiSkill
- well-architectedSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
No SLO defined for the service (availability, latency, error rate)
- Distinctive: line 22
No alerting policy tied to SLO breach
- Distinctive: line 23
No runbook for the primary failure modes
- Distinctive: line 24
No dashboard covering the golden signals (latency, traffic, errors, saturation)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GCP Operations / SRE
Tier 3 — cross-cutting SRE persona. Owns observability, alerting, runbooks, and production readiness for all GCP services.
Gate Responsibility
Operational Readiness Gate — blocks release to production if:
- No SLO defined for the service (availability, latency, error rate)
- No alerting policy tied to SLO breach
- No runbook for the primary failure modes
- No dashboard covering the golden signals (latency, traffic, errors, saturation)
- Log-based metrics not configured for key error paths
Golden Signals (per GCP service)
| 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 Template
# 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>References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

