New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Google Cloud Scc Query

by google in google/skills

Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center.

OfficialApache-2.0Auto-check passed

Install Google Cloud Scc Query

skills CLI
$ npx skills add google/skills --skill google-cloud-scc-query -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install google/skills google-cloud-scc-query --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cloud/google-cloud-scc-query .claude/skills/google-cloud-scc-query && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
google-cloud-scc-query
GitHub stars
21k
Token cost
~3k tokens
SKILL.md length
991 words
Files
2 (incl. references)
Skills in repo
145
Repo updated
First seen
Licence
Apache-2.0

At a glance

Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center.

  • Works in 6 steps: Location Parameterization → API Endpoint Overrides → Location-Qualified Finding Resource Names → …
  • Retrieving details for a security finding by its name
  • SKILL.md covers Core Execution Rules, Data Residency & Regional…, Intent-Based Query Strategies and Payload Analysis & Handoff, plus 1 more section
  • Calls gcloud; reaches securitycenter.eu.rep.googleapis.com

What it does

Google Cloud Scc Query is an agent skill from google/skills, published by the product's own GitHub organization. Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center. Use when retrieving details for a security finding by its name, validating finding scope (e.g., verifying findingClass is TOXICCOMBINATION, VULNERABILITY, EXTERNALEXPOSURE, or THREAT), or fetching finding details for triage. Don't use to draft remediations, apply patches, or execute configurations.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/finding_schema.md`).

It works with Google Cloud. The repository describes itself as: Agent Skills for Google products and technologies. The licence is Apache-2.0.

When your agent uses it

  • Retrieving details for a security finding by its name
  • Validating finding scope (e.g.
  • Verifying findingClass is TOXICCOMBINATION
  • EXTERNALEXPOSURE

Example prompts

  • “Use the google-cloud-scc-query skill to query and retrieves active security findings, external exposures, toxic combinations, vulnerabilities…”
  • “/google-cloud-scc-query”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Location Parameterization
  2. API Endpoint Overrides
  3. Location-Qualified Finding Resource Names
  4. Deep Dive (Specific Finding Details)
  5. Listing (Filtered Projection)
  6. Discovery & Aggregation (Grouping)

What it can do on your machine

Read from SKILL.md and the folder at commit 8a1ac05. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gcloud

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • securitycenter.eu.rep.googleapis.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Cloud Scc Query loads about 3k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 991 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~127
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from google/skills at commit 8a1ac05, republished under its Apache-2.0 licence (© google). 991 words, ~3,046 tokens.

Download SKILL.mdSave it as .claude/skills/google-cloud-scc-query/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
google-cloud-scc-query
description
Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center. Use when retrieving details for a security finding by its name, validating finding scope (e.g., verifying findingClass is TOXIC_COMBINATION, VULNERABILITY, EXTERNAL_EXPOSURE, or THREAT), or fetching finding details for triage. Don't use to draft remediations, apply patches, or execute configurations.
metadata.version
1.0.0
metadata.category
Security

Google Cloud Security Command Center Query Skill

Provides guidelines and read-only gcloud CLI command patterns for querying and retrieving security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center.

[!IMPORTANT] There is NO gcloud scc findings describe command (Invalid choice: 'describe'). To retrieve details for a specific finding by its name, always use gcloud scc findings list with a filter on name.

Core Execution Rules

  1. Read-Only & Zero-Speculation (Parent Scope Required): Keep all executions strictly read-only. Every gcloud scc findings list or group command strictly requires an explicit {parent} scope (organizations/{id}, projects/{id}, or folders/{id}). If the parent scope is missing from the prompt and cannot be inferred from a full finding name, DO NOT run any gcloud commands (do not execute queries without parent, and never inspect gcloud config). Halt immediately before executing commands and ask the user for the parent resource scope.
  2. Bounded Execution & No Runaway Loops:
    • Limit tool calls to what is strictly necessary to complete the query (typically 1 call for direct queries, or 2 calls for List → Deep Dive workflows).
    • If a command fails due to permission/auth errors, or if a specific finding query returns [], halt immediately. Do not attempt blind brute-force retries with different flags, and never search the local workspace for credentials.
  3. Immediate Halt on Errors: If any command fails with PERMISSION_DENIED, IAM_PERMISSION_DENIED, credential expiration, or network timeouts, halt immediately and report the verbatim error message. Do not search the workspace for credentials or run diagnostic loops.
  4. Ambiguous or Multiple Findings: If multiple finding names are provided when a single finding report is requested, or if listing returns multiple findings, do not investigate all of them or unilaterally pick one. Halt immediately without running queries and ask the user to clarify which specific finding name they want details for. If zero findings are returned from a query, report that no active findings exist and halt immediately.
  5. Do Not Query Attack Path Resources: Analyze only the data present in the Security Command Center finding JSON payload. Do not run commands to describe, verify, or query underlying Google Cloud resources (such as VMs, Cloud Storage buckets, service accounts, or IAM policies).
  6. Parent Scope Resolution:
    • For listing and grouping, format the parent resource path as organizations/{org_id}, projects/{project_id}, or folders/{folder_id}.
    • For deep dive queries on a specific finding name, extract the {parent} resource prefix before /sources/...:
      • organizations/{org_id}/sources/... → {parent} is organizations/{org_id}
      • folders/{folder_id}/sources/... → {parent} is folders/{folder_id}
      • projects/{project_id}/sources/... → {parent} is projects/{project_id} Extract the parent prefix regardless of whether the finding resource name is global (4-segment) or location-qualified (5-segment with /locations/{location}/). Execute the deep dive query using the extracted {parent}. Do not reject or halt on project- or folder-level findings.

Data Residency & Regional Endpoints

When Data Residency (DRZ) is enabled, findings are stored and accessible only within their designated regional location (us, eu, or me-central2). Queries across different locations do not return findings from other regions.

1. Location Parameterization

All gcloud scc findings commands require specifying the target location via --location={location}:

  • Default: global (used when data residency is not enabled or for global findings).
  • Supported Regional Locations:
    • us (United States multi-region)
    • eu (European Union multi-region)
    • me-central2 (Kingdom of Saudi Arabia regional location)
2. API Endpoint Overrides

When data residency (DRZ) is enabled for an organization in a regional location (us, eu, or me-central2), configure the regional API endpoint override before executing finding queries:

bash
gcloud config set api_endpoint_overrides/securitycenter https://securitycenter.{LOCATION}.rep.googleapis.com/

Example for the European Union (eu) region:

bash
gcloud config set api_endpoint_overrides/securitycenter https://securitycenter.eu.rep.googleapis.com/

To reset the endpoint back to default global routing:

bash
gcloud config unset api_endpoint_overrides/securitycenter
Show full SKILL.md (411 more words)Show less
3. Location-Qualified Finding Resource Names

Regional finding resource names include the /locations/{location}/ path segment:

  • Organization-level: organizations/{org_id}/sources/{source_id}/locations/{location}/findings/{finding_id}
  • Folder-level: folders/{folder_id}/sources/{source_id}/locations/{location}/findings/{finding_id}
  • Project-level: projects/{project_id}/sources/{source_id}/locations/{location}/findings/{finding_id}

When performing a Deep Dive on a location-qualified finding name:

  1. Extract the {parent} scope (the prefix before /sources/..., e.g., organizations/{org_id}).
  2. Extract the {location} from /locations/{location}/ (e.g., eu, us, me-central2). If not present in the finding name, default to global (or the user-specified location).
  3. Execute the query with --location={location} and --filter="name=\"{finding_name}\"".

Intent-Based Query Strategies

1. Deep Dive (Specific Finding Details)

Intent: User provides a specific finding name or explicitly asks to retrieve all details for one finding.
Action: Execute gcloud scc findings list with a strict filter on name and NO --field-mask to retrieve the complete JSON payload. Specify --location={location} (default global unless a regional location is indicated or present in the finding name).

bash
gcloud scc findings list {parent} \
  --location={location} \
  --filter="name=\"{finding_name}\"" \
  --format="json" --limit=1
2. Listing (Filtered Projection)

Intent: User wants to list active findings matching criteria without pulling full nested payloads.
Action: Use --field-mask projection to restrict output size. Specify --location={location} (default global unless querying a specific region).

bash
gcloud scc findings list {parent} \
  --location={location} \
  --filter="{filter_expression}" \
  --field-mask="finding.name,finding.parentDisplayName,finding.findingClass,finding.category,finding.state,finding.eventTime,finding.severity,finding.resourceName" \
  --format="json" --order-by="severity,event_time desc" --limit=100
Intent / Target Finding Class--filter Expression
All Active Findingsstate="ACTIVE"
Vulnerabilities`state="ACTIVE" AND
: : findingClass="VULNERABILITY"` :
Misconfigurations`state="ACTIVE" AND
: : findingClass="MISCONFIGURATION"` :
Toxic Combinations`state="ACTIVE" AND
: : findingClass="TOXIC_COMBINATION"` :
External Exposures`state="ACTIVE" AND
: : findingClass="EXTERNAL_EXPOSURE"` :
Threatsstate="ACTIVE" AND findingClass="THREAT"
Observations`state="ACTIVE" AND
: : findingClass="OBSERVATION"` :
Sensitive Data Risks`state="ACTIVE" AND
: : findingClass="SENSITIVE_DATA_RISK"` :
Chokepoints`state="ACTIVE" AND
: : findingClass="CHOKEPOINT"` :
Posture Violations`state="ACTIVE" AND
: : findingClass="POSTURE_VIOLATION"` :
Secretsstate="ACTIVE" AND findingClass="SECRET"
SCC Errors`state="ACTIVE" AND
: : findingClass="SCC_ERROR"` :
Specific Categorystate="ACTIVE" AND category="{category}"
3. Discovery & Aggregation (Grouping)

Intent: User wants high-level counts or landscape overview (e.g., "What are the most common findings?", "Show me a summary by category").
Action: Use gcloud scc findings group. Specify --location={location} (default global unless querying a specific region). Allowed fields for --group-by are strictly: resource_name, category, state, parent.

bash
gcloud scc findings group {parent} \
  --location={location} \
  --group-by="{group_by_field}" \
  --filter="state=\"ACTIVE\"" \
  --format="json"

Payload Analysis & Handoff

Once the finding JSON payload is retrieved:

  • For TOXIC_COMBINATION Findings:
    1. Verify the attackExposure field is present and has a score > 0.
    2. Inspect the attack path nodes, edges, or referenced attackExposureResult to identify exposed resources and attack trajectories.
  • For VULNERABILITY Findings:
    1. Extract CVSS scores, exploit signals (exploitationActivity, observedInTheWild, zeroDay), upstream fix status (upstreamFixAvailable), and affected package details from the vulnerability object to evaluate risk:
      • vulnerability.cve.id
      • vulnerability.cve.cvssv3.baseScore
      • vulnerability.cve.cvssv3.attackVector
      • vulnerability.cve.exploitationActivity
      • vulnerability.cve.observedInTheWild
      • vulnerability.cve.zeroDay
      • vulnerability.cve.upstreamFixAvailable
      • vulnerability.offendingPackage.packageName
      • vulnerability.offendingPackage.packageVersion
      • vulnerability.fixedPackage.packageVersion
      • vulnerability.securityBulletin.suggestedUpgradeVersion
  • Handoff: Do not draft remediation plans, patch resources, or execute configuration commands. Pass the extracted finding payload to the appropriate remediation or IAM analyzer skill to manage the remediation action loop.

Reference Schema

See finding_schema.md for the JSON structure of a Security Command Center finding.

© google, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/cloud/google-cloud-scc-query of google/skills.

  • SKILL.md
  • references/finding_schema.md

Open the folder on GitHubat commit 8a1ac05

Compare with similar skills

Google Cloud Scc Query next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Cloud Scc Query compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Google Cloud Scc Query this skillgoogle/skills21k—~3kAutomated safety check: PassApache-2.0
Gmail Inbox Watchergoogleworkspace/cli31k1 repos~476Automated safety check: PassApache-2.0
Cloud Cost Optimizationwshobson/agents40k13 repos~1.7kAutomated safety check: PassMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2596 repos~1.1kAutomated safety check: NotesCustom licence
Terravision Cloud Diagramspatrickchugh/terravision1.6k—~5.6kAutomated safety check: NotesAGPL-3.0-only
Kiln Check DeprecationKiln-AI/Kiln5.2k—~2.5kAutomated safety check: NotesCustom licence

Similar skills

  • Gmail Inbox Watcher

    googleworkspace/cli

    Streams new Gmail messages as NDJSON from the gws command line tool using Google Pub/Sub, with label filters, batch settings and optional per-message files.

    31k GitHub starsUsed in 1 repo~476 tokens
    Productivity & AutomationAuto-check passed

  • Cloud Cost Optimization

    wshobson/agents

    Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 13 repos~1.7k tokens
    DevOps & CloudAuto-check passed

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    259 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Kiln Check Deprecation

    Kiln-AI/Kiln

    Check Kiln's model list for deprecated or sunset models across all providers.

    5.2k GitHub stars~2.5k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes

  • Windmill Trigger Type Checklist

    windmill-labs/windmill

    Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.

    18k GitHub stars~4.7k tokensUpdated today
    Backend & APIsAuto-check passed

More from google/skills

All 145 skills in this repo

  • Google Cloud PAM Helper

    google/skills

    Official

    Manages Google Cloud Privileged Access Manager entitlements and grants: create and edit entitlements, request temporary access, and approve or deny pending grants.

    21k GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Agent Platform Alert Configuration

    google/skills

    Official

    Writes Terraform alerting policies for AI agents that emit OpenTelemetry metrics, covering reliability, cost, safety, security and quality signals on Google Cloud.

    21k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Model Garden Deployment

    google/skills

    Official

    Deploys open models or custom weights from Model Garden to Agent Platform endpoints, checks deployment status and cleans up endpoints, confirming before any change.

    21k GitHub stars~5.1k tokensUpdated today
    Auto-check passed

  • Agent Platform Skill Registry

    google/skills

    Official

    Searches, manages and scaffolds skills in the Gemini Enterprise Agent Platform Skill Registry using bundled Python scripts and Google Cloud credentials.

    21k GitHub stars~584 tokensUpdated today
    Auto-check passed

  • GCP Application Design Center Deploy

    google/skills

    Official

    Designs GCP infrastructure as local Terraform, validates and scans it against best practices, then imports it to Application Design Center for deployment and troubleshooting.

    21k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • BigQuery Slot and Cost Optimizer

    google/skills

    Official

    Analyzes BigQuery slot use, query costs and execution bottlenecks from INFORMATION_SCHEMA to diagnose slow queries, slot contention and unpartitioned scans.

    21k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Questions about Google Cloud Scc Query

What does Google Cloud Scc Query do?

Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center. Google Cloud Scc Query is an agent skill from google/skills, published by the product's own GitHub organization. Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Google Cloud Security Command Center.

When should I use Google Cloud Scc Query?

Google Cloud Scc Query fits situations like: retrieving details for a security finding by its name; validating finding scope (e.g; verifying findingClass is TOXICCOMBINATION; EXTERNALEXPOSURE.

How do I install Google Cloud Scc Query in Claude Code?

Run `npx skills add google/skills --skill google-cloud-scc-query -a claude-code`. Or copy the skill folder (skills/cloud/google-cloud-scc-query in google/skills) into .claude/skills/google-cloud-scc-query in your project. Claude Code loads it when a task matches its description.

How do I install Google Cloud Scc Query in Codex?

Run `npx skills add google/skills --skill google-cloud-scc-query -a codex`. Or copy the skill folder (skills/cloud/google-cloud-scc-query in google/skills) into .agents/skills/google-cloud-scc-query in your project. Codex loads it when a task matches its description.

Can I use Google Cloud Scc Query in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add google/skills --skill google-cloud-scc-query -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-cloud-scc-query, .gemini/skills/google-cloud-scc-query, .github/skills/google-cloud-scc-query and .opencode/skills/google-cloud-scc-query in your project.

What does Google Cloud Scc Query need to run?

Going by SKILL.md and its folder, Google Cloud Scc Query needs the command-line tools its instructions call (gcloud).

Does Google Cloud Scc Query access the network?

SKILL.md names 1 domain. In commands or code: securitycenter.eu.rep.googleapis.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Google Cloud Scc Query safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Google Cloud Scc Query use?

Google Cloud Scc Query is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Cloud Scc Query use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 978 tokens, read only when the agent opens those files.

What are the alternatives to Google Cloud Scc Query?

Skills that share tags, products or a category with Google Cloud Scc Query: Gmail Inbox Watcher (googleworkspace/cli, 31k stars), Cloud Cost Optimization (wshobson/agents, 40k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars) and Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Cloud Scc Query?

google (a GitHub organization, an official publisher) maintains it in google/skills, which has 20,994 GitHub stars. The repository holds 145 skills in this directory. The repository was last updated on October 6, 2026.

Source: google/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.