Skip to content
Skill

Cloud monitoring notification channels configuration

Lets the agent create Cloud Monitoring notification channels and attach them to alert

Install
Scripts
shell
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 notification channels configuration

Cloud monitoring notification channels configuration is an open-source agent skill for communication. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

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.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 10 files (42 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-notification-channels-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-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.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/cloud-monitoring-notification-channels-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-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.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/cloud-monitoring-notification-channels-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-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.

Cursor docs on skills

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-notification-channels-configuration

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

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/cloud-monitoring-notification-channels-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-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.

VS Code docs on skills

Get the folder:

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.

The SKILL.md format

What it does

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

Cloud monitoring notification channels configuration 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.

More from google/skills

  1. Route platform choices to Google's own skills by fetching and filtering its skill catalog

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

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

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

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  5. Look up Google developer docs through the Developer Knowledge MCP server or REST fallback

    • Open source
    • 24.4K GitHub stars
    • Developer tools