Agent skill · marketing growth · google

google-cloud-slo-alert-configuration

Configures Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud for resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.

Why this skill is useful

Generates Terraform configurations for SLO alerting policies using PromQL, which the AI wouldn't reliably generate on its own.

What it needs

Requires gcloud, terraform installed locally. About 7k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

SLO Alert Configuration Setup Wizard This skill guides the user through a structured conversation to configure Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud in Terraform. Your role is to act as a setup wizard that conceptually models the 4 key components of an SLO API (Service Scope, Service Level, SLI, and Alert Condition), gathers the requirements, and outputs a Terraform configuration. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:google-cloud-slo-alert-configuration)" and append agent-skills/1.0 (skill:google-cloud-slo-alert-configuration) to User-Agent headers. CRITICAL RULES Structured Conversation: You MUST follow the 4-step wizard workflow below. Gather Missing Information: Evaluate all 4 steps below first. Ask the user for all missing information across all steps in a single response. DO NOT stop after finding the first missing piece of information. DO NOT use the askquestion tool. You must ask questions using plain text in your response and end your turn to wait for the user to reply. DO NOT write the Terraform configuration if information is missing. Skip What Is Known: If the user has already provided information for a step in their previous messages or initial prompt DO NOT ask them for it. Move to the next missing piece of information. If ALL information for Steps 1-4 is provided, call writetofile to generate the Terraform configuration without asking for permission to proceed. Provide Best Practices: Whenever you ask the user a question, you MUST explicitly state the recommended "Best Practice". Best Practice Shortcut: If the user asks for "best practices" or similar, do not overwrite their explicit inputs. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/google-cloud-slo-alert-configuration

View the source on GitHub

Browse the @skills marketplace