Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

cloud-monitoring-metric-selection

skill · google/skillsApache-2.0 licenceAudited 13 Nov 2026 · source 19363c4898c3

★ 24,090pushed todayversion 1.0.2
✓SAFEGrade B · 89/100 · 13 Nov 2026 · 19363c4
24,090repo stars · whole google/skills

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 19363c4898c3 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “cloud-monitoring-metric-selection (google/skills)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/google/cloud-monitoring-metric-selection

Trust audit

Audit 0.4.1 · source read 13 Nov 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 19363c4898c3 · 13 Nov 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publishergoogle GitHub organizationOwner of the repository this skill is read from
  • Source foldergoogle/skills/skills/cloud/cloud-monitoring-metric-selectionThe exact folder we audited
  • LicenceApache-2.0As the repository states it
  • Commit pinned for this verdict19363c4898c3A new audit runs when the source changes
  • Repository statusNot archivedPushed today
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: 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…

---
name: cloud-monitoring-metric-selection
metadata:
  version: "1.0.2"
  category: CloudObservabilityAndMonitoring
description: >-
  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.
---

# 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](references/attribution.md). For commands executed
directly in the terminal (never in generated scripts, Terraform, or user code),
prefix `gcloud` with
`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="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 `list_metric_descriptors` MCP
    tool.
*   **Mandatory Project ID and Resource Parameter Clarification**: BEFORE
    calling any API tools (such as `list_metric_descriptors`), 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 `YOUR_PROJECT_ID`).
*   **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 `list_metric_descriptors` (such as
    `google-cloud-monitoring:list_metric_descriptors`,
    `mcp_google-cloud-monitoring_list_metric_descriptors`, or a similar pattern)
    is available in your active toolset.
2.  **Verify via Unique URL**: To ensure you are calling the correct Cloud
    Monitoring tool, confirm that the underlying MCP server configuration
    points to: **`https://monitoring.googleapis.com/mcp`**.
3.  If the tool is **missing**:

    *   Locate the MCP configuration file for the user's environment. Check
        common paths:
        -   `~/.gemini/config/mcp_config.json`
        -   `~/.codeium/windsurf/mcp_config.json`
        -   `cline_mcp_settings.json`
        -   `claude_desktop_config.json`
    *   Directly update/merge the configuration file with the following server
        configuration. **CRITICAL**: Merge the JSON object to preserve any
        existing MCP servers in `mcpServers`. Do not overwrite the file.

        ```json
        "google-cloud-monitoring": {
          "url": "https://monitoring.googleapis.com/mcp",
          "authProviderType": "google_credentials",
          "enabledTools": [
            "list_metric_descriptors"
          ]
        }
        ```

    *   Print a clear message notifying the user that the
        `google-cloud-monitoring` MCP server has been configured, and request
        them to restart or start a new chat session to refresh tools. Stop
        calling further tools and end the turn.

### Step 2: Analyze Request & Extract Keywords

1.  **Resolve Project ID and Identifiers**: Check for the GCP Project ID and
    resource identifiers in the prompt, resource URIs, or environment context.
    According to the CRITICAL RULES above, do NOT use placeholder project names.

2.  **Identify Service Prefix**: Map target GCP services to their standard
    prefix (such as `compute`, `spanner`, `bigquery`, `storage`).

3.  **Extract Metric Concepts**: Extract metric keywords from user prompt (such
    as "CPU", "memory", "bytes scanned", "latency", "connections") and map to
    search substrings.

*Example Query Analysis:*

*   **User Prompt**: "Check Cloud Storage bucket write throughput and request
    count"
*   **Resource URI**:
    `//storage.googleapis.com/projects/my-project/buckets/my-bucket`
*   **Service Prefix**: `storage` (mapped to `storage.googleapis.com`)
*   **Metric Keywords**: `write`, `throughput`, `request`, `count`
*   **Mapped Substrings**: `write`, `throughput`, `request_count`, `count`

### Step 3: Query Metric Descriptors via list_metric_descriptors Tool

Query all metric descriptors for each identified service prefix using the
`list_metric_descriptors` MCP tool (using `pageSize: 200`). Because Cloud
Monitoring filters do not allow combining multiple `metric.type` restrictions
with `OR`, you must **initiate a separate query for each identified service
prefix** (either sequentially or in parallel).

If any response includes a `nextPageToken`, you MUST make consecutive follow-up
calls passing `pageToken` until all remaining descriptors for that prefix are
retrieved before filtering.

*Filter Pattern Construction:* Map the target service domain to its appropriate
prefix style:

1.  **Standard Google Cloud Services**:
    `starts_with("<service_prefix>.googleapis.com/")` (such as
    `bigquery.googleapis.com/`, `redis.googleapis.com/`).
2.  **Ops Agent (Guest OS)**: `starts_with("agent.googleapis.com/")` (for guest
    OS memory/disk metrics).
3.  **Kubernetes / GKE Native**: `starts_with("kubernetes.io/")`
4.  **Istio Service Mesh**: `starts_with("istio.io/")`
5.  **Knative Serving / Autoscaler**: `starts_with("knative.dev/")`
6.  **Custom / External Metrics**: Use 

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 19363c4

Download folder ↗
git clone https://github.com/google/skills
git -C skills checkout 19363c4898c3

The author documents no install command, so this uses the repository directly. Our verdict covers commit 19363c4898c3 only.

Works in which agents?

What its own text says, not a test

AgentStatusMore
WindsurfMentioned in its text, not testedSkills for Windsurf · About Windsurf
“Mentioned” means the skill’s text names the agent. We have not run it there.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 19363c4898c3

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/google/cloud-monitoring-metric-selection/badge.svg)](https://modelsatlas.com/skills/google/cloud-monitoring-metric-selection/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

cloud-sql-basics✓SAFE

google/skills

This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server.

★ 24kGrade B
cloud-run-basics✓SAFE

google/skills

Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based…

★ 24kGrade B
cloud-logging-configuration-basics✓SAFE

google/skills

Configure single-project Cloud Logging on Google Cloud: regional log buckets, log sinks, log views, restricting or hiding sensitive logs in the default view (_Default) filter, IAM permissions for views (Logs View…

★ 22kGrade B
cloud-logging-query-generation✓SAFE

google/skills

Generates Logging Query Language (LQL) queries for Cloud Logging on Google Cloud from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google…

★ 22kGrade B
bigquery-bigframes✓SAFE

google/skills

Generates Python code using BigQuery DataFrames (BigFrames). Use by default for any Python data task involving BigQuery, including data processing, analysis, and machine learning. Don't use for SQL-first workflows or…

★ 22kGrade B
bigtable-basics✓SAFE

google/skills

Assists in provisioning instances/tables, designing performant schemas, and querying data in Bigtable. Use when designing Bigtable row keys, configuring column families, writing SQL queries or client library code (Java,…

★ 22kGrade B

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/google/cloud-monitoring-metric-selection/badge.svg)](https://modelsatlas.com/skills/google/cloud-monitoring-metric-selection/)

Questions about cloud-monitoring-metric-selection

What does the cloud-monitoring-metric-selection skill do?
Agent Skills for Google products and technologies
Is cloud-monitoring-metric-selection safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can cloud-monitoring-metric-selection access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does cloud-monitoring-metric-selection work with?
Its documentation mentions windsurf. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (19363c4898c3), read on 2026-11-13. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.