
Cloud monitoring list time series request
Builds valid Cloud Monitoring ListTimeSeries requests, filters and aggregations
- Scripts
- None
- 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 list time series request
Cloud monitoring list time series request is an open-source agent skill for cloud and infrastructure. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.
This skill helps an agent turn a Cloud Monitoring metric descriptor and a set of resource parameters into a ready-to-run ListTimeSeries REST query. It covers the name, filter, interval, aggregation and view parameters, and it works through the metric's kind and value type to pick a suitable per-series aligner and cross-series reducer.
The workflow reuses metric metadata already supplied by the user, looks up missing descriptors through a metric-selection companion skill or the list_metric_descriptors tool, and builds filters with the correct resource.labels and metric.labels prefixes. It sets the alignment period from the lookback window and defaults to a one-hour interval when none is given. Before returning output, the agent is told to check the request against the list_timeseries tool using the HEADERS view.
The skill expects a GCP project ID, either given directly or resolvable from the local gcloud configuration, and access to Cloud Monitoring tools or the REST API. It includes a usage attribution step for gcloud commands and bundles reference files on aggregation combinations.
When your agent uses it
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.
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 3 files (24 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-list-time-series-request 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-list-time-series-request &&
cp -R "$tmp/skills/cloud/cloud-monitoring-list-time-series-request" ~/.claude/skills/cloud-monitoring-list-time-series-request &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/cloud-monitoring-list-time-series-request inside it instead.
Copy the skill folder to ~/.agents/skills/cloud-monitoring-list-time-series-request 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-list-time-series-request &&
cp -R "$tmp/skills/cloud/cloud-monitoring-list-time-series-request" ~/.agents/skills/cloud-monitoring-list-time-series-request &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/cloud-monitoring-list-time-series-request inside it instead.
Copy the skill folder to ~/.cursor/skills/cloud-monitoring-list-time-series-request 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-list-time-series-request &&
cp -R "$tmp/skills/cloud/cloud-monitoring-list-time-series-request" ~/.cursor/skills/cloud-monitoring-list-time-series-request &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/cloud-monitoring-list-time-series-request inside it instead.
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-list-time-series-requestOr copy the folder to ~/.gemini/skills/cloud-monitoring-list-time-series-request yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/cloud-monitoring-list-time-series-request:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/cloud-monitoring-list-time-series-request &&
cp -R "$tmp/skills/cloud/cloud-monitoring-list-time-series-request" ~/.copilot/skills/cloud-monitoring-list-time-series-request &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/cloud-monitoring-list-time-series-request inside it instead.
Get the folder:
git clone --depth 1 https://github.com/google/skills.gitThen copy skills/skills/cloud/cloud-monitoring-list-time-series-request into your agent's skills folder as cloud-monitoring-list-time-series-request. Agents that support SKILL.md read one folder per skill.
What it does
- Filter expression construction
- Builds Cloud Monitoring filters with the correct metric type, resource type and label prefixes.
- Aligner and reducer selection
- Chooses per-series aligners and cross-series reducers based on metric kind and value type.
- Automatic alignment period
- Derives the alignment period from the start and end times of the query window.
- Metric descriptor lookup
- Fills in missing metric type, kind and value type details from descriptors or a companion skill.
- Request validation step
- Checks generated parameters against the list_timeseries tool before returning them.
Good for
- Generate a ListTimeSeries request for VM CPU utilization over the last hour
- Build a filter for a Cloud SQL database metric scoped to one instance
- Create an aggregation that groups disk usage by zone
- Format a JSON payload for a Cloud Monitoring chart query
Cloud monitoring list time series request FAQ
Does it need a Google Cloud project ID?
Yes. The skill requires a project ID from the prompt, input or environment, and asks the user for one when it cannot be resolved.
What happens if no time range is given?
It computes a one-hour lookback ending at the current time and uses a 60s alignment period for that window.
Does it discover which metric to use?
No. Metric discovery and selection are excluded; for vague requests it defers to the cloud-monitoring-metric-selection skill.
Does it run queries against Cloud Monitoring?
It calls the list_timeseries tool with the HEADERS view to validate the generated request structure.
How do I install Cloud monitoring list time series request in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/cloud-monitoring-list-time-series-request to use it in all your projects, or to .claude/skills/cloud-monitoring-list-time-series-request in one project.
Does Cloud monitoring list time series request run scripts?
No. It is instructions only, with no 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 list time series request?
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 list time series request?
The closest alternatives to Cloud monitoring list time series request are AWS cloudwatch investigation, AWS resource health diagnose, Cloud monitoring metric selection, Cloud monitoring promql query and Cloud monitoring alert configuration.
Where this comes from
- Description: from the skill's own SKILL.md.
More from google/skills

Route platform choices to Google's own skills by fetching and filtering its skill catalog
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

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

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

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

Look up Google developer docs through the Developer Knowledge MCP server or REST fallback
- Open source
- 24.4K GitHub stars
- Developer tools

Add, remove or clear audience members with the Google Data Manager API
- Open source
- 24.4K GitHub stars
- Marketing and SEO




