Agent skill · data analytics · google
cloud-monitoring-metric-selection
Retrieve, query, and identify relevant Cloud Monitoring metric descriptors on Google Cloud for a service or resource (such as Compute Engine, Spanner, BigQuery, Cloud Run, Cloud SQL, Pub/Sub, Cloud Storage, etc.). Use when asked to find, list, search, or discover GCP metric types, names, kind/value schemas, or descriptors.
Why this skill is useful
Provides specific commands and workflows for querying Google Cloud Monitoring metrics that the AI wouldn't reliably generate on its own.
What it needs
Requires google_cloud account access. About 5k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
Metric Selection (Service Query & Local Keyword Filtering) Use this skill to identify the most relevant Cloud Monitoring metric descriptors. It queries all metric descriptors for a target service from the API and filters them locally inside the agent's context using keyword matching. 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:cloud-monitoring-metric-selection)" and append agent-skills/1.0 (skill:cloud-monitoring-metric-selection) to User-Agent headers. CRITICAL RULES Always Query Live APIs: You MUST always retrieve the most up-to-date metric descriptors dynamically by calling the listmetricdescriptors MCP tool. Mandatory Project ID and Resource Parameter Clarification: BEFORE calling any API tools (such as listmetricdescriptors), you MUST ensure the GCP Project ID is provided in the prompt, URI, or environment context. If the Project ID cannot be resolved, you MUST ask the user to clarify or provide it BEFORE executing API queries. Do NOT run API queries against unconfirmed default or placeholder project names (such as mock-project, my-project-id, unused, or YOURPROJECTID). Fallback Reporting: If API calls fail and fallback sources (such as public docs) are used, you MUST state the error, the fallback source, and the risks of non-live data (such as potential staleness, missing custom metrics, or schema mismatches). Workflow Step 1: Verify & Auto-Configure MCP 1. Check if any tool matching listmetricdescriptors (such as google-cloud-monitoring:listmetricdescriptors, mcpgoogle-cloud-monitoringlistmetricdescriptors, or a similar pattern) is available in your active toolset. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/cloud-monitoring-metric-selection