Gcp ops

Skill jpantsjoha/googlecloud-plugin/skills/gcp-ops

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.From its SKILL.md

Install

npx -y skills add jpantsjoha/googlecloud-plugin --skill gcp-ops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, as published. Nobody here has run it

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>