Agent skill · google
cloud-monitoring-list-time-series-request
Generates valid Cloud Monitoring ListTimeSeries requests and aggregation specifications from metric descriptors and resource parameters. Use when asked to create, generate, format, or build ListTimeSeries requests, JSON payloads, filter expressions, or aligner/reducer aggregations for Cloud Monitoring metrics and charts. Don't use for metric discovery or metric selection.
What it needs
About 5k tokens when loaded.
What this skill does
Cloud Monitoring ListTimeSeries Request Generator Use this skill to translate any Cloud Monitoring metric descriptor into valid, production-ready ListTimeSeries REST API query parameters (name, filter, interval.startTime, interval.endTime, aggregation., view). 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-list-time-series-request)" and append agent-skills/1.0 (skill:cloud-monitoring-list-time-series-request) to User-Agent headers. CRITICAL RULES Mandatory Project ID Clarification: You MUST ensure the GCP Project ID is present in the user prompt, input payload, or environment context (such as via gcloud config get-value project). If the Project ID is missing and cannot be resolved, you MUST ask the user to clarify it before generating or executing ListTimeSeries requests. Do NOT use placeholders for project names. Workflow Inspect Metric Metadata 1. Use Provided Metric Metadata First: If the user's prompt already includes metric metadata such as metric.type, metricKind, valueType, resource types, or label keys, use those values directly instead of calling API tools. 2. Discover Missing Metadata: If exact metric descriptors including metric.type, metricKind, and valueType are missing or underspecified, resolve the target metric's descriptor using one of these paths: Vague Query: If the prompt is vague, such as asking for VM CPU usage, use the cloud-monitoring-metric-selection skill first to identify the specific metric type. Known Metric Type: If you already have the specific metric type name such as compute.googleapis.com/instance/cpu/utilization, but need its descriptor, call the listmetricdescriptors MCP tool. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/cloud-monitoring-list-time-series-request