
Cloud monitoring alert configuration
Generates Terraform and PromQL Cloud Monitoring alerting policies for Google Cloud
- Scripts
- Python
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 24.4K
- Last commit
- 2 days ago
- License
- Apache-2.0
- Listing updated
- 1 day ago
Similar skills
About Cloud monitoring alert configuration
Cloud monitoring alert configuration is an open-source agent skill for cloud and infrastructure. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.
This skill guides an agent through creating, reviewing, migrating and deduplicating Cloud Monitoring alerting policies written as Terraform google_monitoring_alert_policy resources. It covers Cloud Run services, jobs and worker pools, GKE workloads, Compute Engine and AI Hypercomputer reservations, Vertex AI Agent Engine telemetry and generic Google Cloud resources, with per-resource reference files that describe the signals to watch and the PromQL to use. The agent is steered toward golden-signal coverage, parameterized thresholds and grouping by resource labels rather than hardcoded instance names.
The skill includes Python helper scripts for schema discovery, PromQL linting, Terraform syntax checks, duplicate detection and agent telemetry checks. It requires explicit user confirmation before any command that changes infrastructure, enables telemetry or applies Terraform. Generated policies are tagged with a user_labels attribution entry, and the agent reminds the user when no notification channels are attached. SLO and burn-rate work is handed off to a separate SLO skill, and notification channel and standalone PromQL tasks go to their own companion skills.
Users should expect to supply their Google Cloud project, target resource details and, for agent monitoring, OpenTelemetry-instrumented workloads. The skill is Apache-2.0 licensed and is part of Google's public skills repository.
When your agent uses it
Configures Cloud Monitoring alerting policies using Terraform and PromQL across Cloud Run, Google Kubernetes Engine (GKE), Compute Engine, AI Hypercomputer reservations, Vertex AI Agent Engine, and generic Google Cloud resources. Use when creating, reviewing, migrating, or deduplicating Terraform alerting policies for latency, traffic, error rates, saturation, host or reservation maintenance, GPU XID insights, or AI agent telemetry. Don't use for standalone PromQL query authoring without alerting, log querying, or billing cost audits.
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
- Runs Python scripts(see the files on GitHub)
- Network calls found in its scripts(see the files on GitHub)
- License: Apache-2.0(see the files on GitHub)
From a static check of its 41 files (517 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Check another skill before you install it.
Install
Copy the skill folder to ~/.claude/skills/cloud-monitoring-alert-configuration to use it in all your projects:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/cloud-monitoring-alert-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-alert-configuration" ~/.claude/skills/cloud-monitoring-alert-configuration &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/cloud-monitoring-alert-configuration inside it instead.
Copy the skill folder to ~/.agents/skills/cloud-monitoring-alert-configuration to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/cloud-monitoring-alert-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-alert-configuration" ~/.agents/skills/cloud-monitoring-alert-configuration &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/cloud-monitoring-alert-configuration inside it instead.
Copy the skill folder to ~/.cursor/skills/cloud-monitoring-alert-configuration to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/cloud-monitoring-alert-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-alert-configuration" ~/.cursor/skills/cloud-monitoring-alert-configuration &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/cloud-monitoring-alert-configuration inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/google/skills.git --path skills/cloud/cloud-monitoring-alert-configurationOr copy the folder to ~/.gemini/skills/cloud-monitoring-alert-configuration yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/cloud-monitoring-alert-configuration:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/cloud-monitoring-alert-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-alert-configuration" ~/.copilot/skills/cloud-monitoring-alert-configuration &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/cloud-monitoring-alert-configuration inside it instead.
Get the folder:
git clone --depth 1 https://github.com/google/skills.gitThen copy skills/skills/cloud/cloud-monitoring-alert-configuration into your agent's skills folder as cloud-monitoring-alert-configuration. Agents that support SKILL.md read one folder per skill.
What it does
- Golden signal coverage
- Builds alerts for latency, traffic, errors and saturation on the target workload.
- Terraform policy generation
- Produces parameterized google_monitoring_alert_policy HCL with attribution labels.
- PromQL alert conditions
- Writes Prometheus Query Language conditions and lints them with a bundled script.
- Per-platform references
- Separate guides for Cloud Run, GKE, Compute Engine, generic resources and AI agents.
- AI agent telemetry alerts
- Covers reliability, quality, cost, safety and security policies for Vertex AI Agent Engine.
- Duplicate and migration review
- Scans existing alerting configurations for duplicates and helps migrate them from MQL.
- Confirmation before changes
- Pauses for explicit approval before running commands that modify infrastructure.
Good for
- Create latency and error-rate alerts for a Cloud Run service
- Review Terraform alerting policies for duplicates
- Set up GKE saturation alerts with PromQL
- Alert on GPU XID insights and host maintenance events
- Monitor Vertex AI Agent Engine cost and reliability
Cloud monitoring alert configuration FAQ
Does it change my Google Cloud resources on its own?
No. The skill requires explicit user confirmation before running commands that modify infrastructure, enable telemetry or apply Terraform.
Which resources does it cover?
Cloud Run services, jobs and worker pools, GKE, Compute Engine, AI Hypercomputer reservations, Vertex AI Agent Engine and generic Google Cloud resources.
What should I use for SLO alerts?
SLO and burn-rate policies are delegated to the google-cloud-slo-alert-configuration skill, except for Agent Platform, where this skill keeps its own burn-rate policies.
Does it attach notification channels?
It does not attach them itself. It reminds the user when no channels are specified and points to a separate notification channels skill.
How do I install Cloud monitoring alert configuration in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/cloud-monitoring-alert-configuration to use it in all your projects, or to .claude/skills/cloud-monitoring-alert-configuration in one project.
Does Cloud monitoring alert configuration run scripts?
Yes. It runs Python scripts. Its scripts contain network calls. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use Cloud monitoring alert configuration?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
What are the best alternatives to Cloud monitoring alert configuration?
The closest alternatives to Cloud monitoring alert configuration are Cloud run alert configuration, Gke alert configuration, Google cloud slo alert configuration, Cloud monitoring notification channels configuration and Cloud monitoring promql query.
Where this comes from
- Description: from the skill's own SKILL.md.
More from google/skills

Route platform choices to Google's own skills by fetching and filtering its skill catalog
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Guardrails for gcloud commands: validate syntax with help, scope projects, dry-run first
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Authenticate to Google Cloud: ADC, impersonation, service accounts and IAM roles
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

First-time Google Cloud setup: sign in, pick a project, link billing, with consent gates
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Look up Google developer docs through the Developer Knowledge MCP server or REST fallback
- Open source
- 24.4K GitHub stars
- Developer tools

Add, remove or clear audience members with the Google Data Manager API
- Open source
- 24.4K GitHub stars
- Marketing and SEO



