agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/gcp-ops/SKILL.md

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.

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
  1. Distinctive:

    No SLO defined for the service (availability, latency, error rate)

    line 21
  2. Distinctive:

    No alerting policy tied to SLO breach

    line 22
  3. Distinctive:

    No runbook for the primary failure modes

    line 23
  4. Distinctive:

    No dashboard covering the golden signals (latency, traffic, errors, saturation)

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

SignalCloud RunGKEBigQueryCloud Storage
Latencyrequest latency p50/p99pod request latencyquery durationobject read latency
Trafficrequest countRPS per podbytes processedobject operations
Errors5xx ratepod restart countjob failure count4xx/5xx rate
Saturationinstance count vs maxnode CPU/memslot 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.