Skip to content

Cloud Monitoring Notification Channels

Generates Terraform for Google Cloud Monitoring alert notification channels (email, SMS, Slack, PagerDuty, Pub/Sub, webhook)

Repository
google/skills
Stars
21,782
Licence
Apache-2.0
Files
9 files

What it does

When installed, the agent can write Terraform configuration files that set up Google Cloud Monitoring notification channels, the destinations that receive alerts such as email, SMS, Slack, PagerDuty, Pub/Sub or webhooks, and attach them to alerting policies. For Pub/Sub channels it also runs a bundled script to check that the topic exists, the Monitoring service agent can publish to it, and related settings are correct. It follows Google's guidance on permissions, project setup and attribution, and it tells the agent not to edit alert conditions or write PromQL or Monitoring filter queries.

Great for

  • Platform or SRE engineers who manage Google Cloud alerting as Terraform code
  • Teams adding Slack, PagerDuty or Pub/Sub destinations to existing Cloud Monitoring alert policies

Skip it if

  • Writing or changing alert conditions, metric selection or PromQL/Monitoring filter queries, which the skill explicitly excludes
  • Non-Terraform setups, since the skill only outputs .tf files and will not create channels by clicking in the console or with other tools

Try asking

  • “Create an email and a Slack notification channel in Terraform and attach them to my existing high-CPU alert policy”
  • “Set up a PagerDuty notification channel for the production project in monitoring/notification_channels.tf”
  • “Check whether my Pub/Sub topic in another project is ready to receive Cloud Monitoring alerts”
Step-by-step guide: how to use Cloud Monitoring Notification ChannelsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 9 original files, the Apache-2.0 licence and an attribution note.

    cloud-monitoring-notification-channels-configuration.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip cloud-monitoring-notification-channels-configuration.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip cloud-monitoring-notification-channels-configuration.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Ask for Terraform generation only if you do not want deployment; the skill will then avoid running gcloud or installing Terraform.
  • Review the generated .tf files and run terraform plan before any apply, since channels and policy changes affect production alerting.
  • Give the project ID and, for Pub/Sub, the full topic path (projects/PROJECT/topics/TOPIC) to avoid prompts and cross-project mistakes.

What's inside

  • references/attribution.md
  • references/email.md
  • references/pagerduty.md
  • references/pubsub.md
  • references/slack.md
  • references/sms.md
  • references/webhook.md
  • scripts/verify_pubsub_topic.sh
  • SKILL.md

Redistributed unmodified from google/skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.