# Cloud monitoring notification channels configuration

> Cloud monitoring notification channels configuration is an open-source agent skill for communication. Lets the agent create Cloud Monitoring notification channels and attach them to alert. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/google/skills/tree/main/skills/cloud/cloud-monitoring-notification-channels-configuration
- **Repository:** https://github.com/google/skills
- **GitHub stars:** 24,379
- **License:** Apache-2.0
- **Skill name:** cloud-monitoring-notification-channels-configuration
- **Collection:** https://github.com/google/skills
- **Categories:** [communication](https://ai-powered.com/categories/communication), [cloud and infrastructure](https://ai-powered.com/categories/cloud-and-infrastructure)
- **Listing updated:** 2026-11-18

## About

This skill guides the agent through writing Terraform HCL for Google Cloud Monitoring notification channels, covering email, SMS, Slack, PagerDuty, Pub/Sub and webhook targets. Each channel type has its own reference file with a Terraform template, and the agent fills in the variables, writes the result to a notification_channels.tf file, and can add an existing channel to a google_monitoring_alert_policy resource.

Before deploying, the agent checks prerequisites such as the project ID and number, gcloud and Application Default Credentials, billing, and the IAM roles needed to manage channels. For Pub/Sub targets, a bundled bash script verifies that the Pub/Sub API is enabled, that the Monitoring service agent can publish to the topic, and that the topic has no message storage policy or in-transit enforcement. Sensitive values are kept in a secret.tfvars file that the agent creates from a template when missing.

The skill requires gcloud, Terraform and a Google Cloud project for deployment, and it tags every resource and command it produces with attribution labels. It does not cover writing alert policy conditions or PromQL and Monitoring Filter queries.

## When your agent uses it

> Generates Terraform HCL configurations for Cloud Monitoring notification channels (`google_monitoring_notification_channel`) and adds notification channels to alerting policies (`google_monitoring_alert_policy`) in Google Cloud projects. Use when creating or configuring email, SMS, Slack, PagerDuty, Pub/Sub, or webhook notification channels, verifying Pub/Sub topic compatibility (including cross-project topics, message storage policies, and in-transit enforcement) and publishing permissions for the Cloud Monitoring Service Agent, or adding notification channels to existing alert policies. Don't use for authoring or editing alerting policy conditions, selecting metric descriptors, or writing PromQL or Monitoring Filter queries.

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Runs shell scripts](https://github.com/google/skills/tree/HEAD/skills/cloud/cloud-monitoring-notification-channels-configuration)
- [No network calls found in its scripts](https://github.com/google/skills/tree/HEAD/skills/cloud/cloud-monitoring-notification-channels-configuration)
- [License: Apache-2.0](https://github.com/google/skills/tree/HEAD/skills/cloud/cloud-monitoring-notification-channels-configuration)

## Features

- **Terraform channel templates:** Reference templates generate google_monitoring_notification_channel resources for email, SMS, Slack, PagerDuty, Pub/Sub and webhooks.
- **Alert policy attachment:** Adds an existing notification channel to a google_monitoring_alert_policy without altering its conditions.
- **Pub/Sub topic verification:** A bash script checks API enablement, publisher permissions and storage or in-transit settings on the topic.
- **Prerequisite checks:** Confirms project identity, gcloud authentication, billing and the IAM roles needed before deployment.
- **Credential file handling:** Creates a secret.tfvars template when missing and checks required credentials before use.
- **Deployment safeguards:** Sets a 120-second timeout and a single targeted retry for Terraform plan and apply runs.

## Good for

- Create an email notification channel for an alerting policy in Terraform
- Send Cloud Monitoring alerts to a Slack channel
- Route monitoring alerts to PagerDuty
- Check that a Pub/Sub topic can receive Cloud Monitoring notifications
- Attach an existing notification channel to an existing alert policy

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/cloud-monitoring-notification-channels-configuration` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/cloud-monitoring-notification-channels-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-notification-channels-configuration" ~/.claude/skills/cloud-monitoring-notification-channels-configuration &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/cloud-monitoring-notification-channels-configuration` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/cloud-monitoring-notification-channels-configuration` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/cloud-monitoring-notification-channels-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-notification-channels-configuration" ~/.agents/skills/cloud-monitoring-notification-channels-configuration &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/cloud-monitoring-notification-channels-configuration` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/cloud-monitoring-notification-channels-configuration` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/cloud-monitoring-notification-channels-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-notification-channels-configuration" ~/.cursor/skills/cloud-monitoring-notification-channels-configuration &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/cloud-monitoring-notification-channels-configuration` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/google/skills.git --path skills/cloud/cloud-monitoring-notification-channels-configuration
```

Or copy the folder to `~/.gemini/skills/cloud-monitoring-notification-channels-configuration` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/cloud-monitoring-notification-channels-configuration`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/cloud-monitoring-notification-channels-configuration &&
cp -R "$tmp/skills/cloud/cloud-monitoring-notification-channels-configuration" ~/.copilot/skills/cloud-monitoring-notification-channels-configuration &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/cloud-monitoring-notification-channels-configuration` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/google/skills.git
```

Then copy `skills/skills/cloud/cloud-monitoring-notification-channels-configuration` into your agent's skills folder as `cloud-monitoring-notification-channels-configuration`. Agents that support SKILL.md read one folder per skill.

## FAQ

### What does the skill need before it can deploy channels?

It needs gcloud authenticated with Application Default Credentials for Terraform, a target project with billing enabled, and IAM permissions for notification channels, either the notificationChannelEditor role or an equivalent custom role.

### Does it write alerting policy conditions?

No. The skill explicitly excludes authoring or editing alerting policy conditions, selecting metric descriptors, and writing PromQL or Monitoring Filter queries.

### Which Pub/Sub topics can be used as a channel?

The bundled verification script checks that the Pub/Sub API is enabled, the Monitoring service agent holds the publisher role, and the topic has no message storage policy and no in-transit enforcement, since Cloud Monitoring cannot deliver to such topics.

### Where are the generated files written?

If no path is given, the skill searches the workspace for existing monitoring, ops or sre directories, and otherwise creates monitoring/notification_channels.tf.

### How do I install Cloud monitoring notification channels configuration in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/cloud-monitoring-notification-channels-configuration to use it in all your projects, or to .claude/skills/cloud-monitoring-notification-channels-configuration in one project.

### Does Cloud monitoring notification channels configuration run scripts?

Yes. It runs shell scripts. No network calls were found in its scripts. 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 notification channels 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 notification channels configuration?

The closest alternatives to Cloud monitoring notification channels configuration are Cloud monitoring alert configuration, Cloud run alert configuration, Google cloud recipe onboarding, Google cloud slo alert configuration and Gke alert configuration.

## Where this comes from

- Description: from the skill's own SKILL.md.

## Alternatives

- [Cloud monitoring alert configuration](https://ai-powered.com/skills/cloud-monitoring-alert-configuration): Cloud monitoring alert configuration is an open-source agent skill for cloud and infrastructure.
- [Cloud run alert configuration](https://ai-powered.com/skills/cloud-run-alert-configuration): Cloud run alert configuration is an open-source agent skill for cloud and infrastructure.
- [Google cloud recipe onboarding](https://ai-powered.com/skills/google-cloud-recipe-onboarding): Google cloud recipe onboarding is an open-source agent skill for cloud and infrastructure.
- [Google cloud slo alert configuration](https://ai-powered.com/skills/google-cloud-slo-alert-configuration): Google cloud slo alert configuration is an open-source agent skill for cloud and infrastructure.
- [Gke alert configuration](https://ai-powered.com/skills/gke-alert-configuration): Gke alert configuration is an open-source agent skill for cloud and infrastructure.
- [Cloud network insights](https://ai-powered.com/skills/cloud-network-insights): Cloud network insights is an open-source agent skill for cloud and infrastructure.
- [Gke observability](https://ai-powered.com/skills/gke-observability): Gke observability is an open-source agent skill for cloud and infrastructure.
- [Agent platform alert configuration](https://ai-powered.com/skills/agent-platform-alert-configuration): Agent platform alert configuration is an open-source agent skill for cloud and infrastructure.

---
Source: https://ai-powered.com/skills/cloud-monitoring-notification-channels-configuration
