Index of every page on this site: llms.txt
All skills
google avatar

/google-cloud-networking-observability

@5fb62c2
by googlegoogle/skills24k stars
2,026
Run it yourself

Investigates Google Cloud networking issues by analyzing GCP logs, metrics, and diagnostics. Use when investigating dropped network traffic, packet drops, drop reasons, VPC Flow Logs (including Private Service Connect / PSC, serverless / App Engine Direct VPC, and cost estimation), Cloud NAT, firewall or threat logs, VPN metrics/tunnels, or Connectivity Tests for path diagnostics. Don't use for generic VM management or non-observability tasks.

Use this Skill: https://skilld.dev/gh/google/skills/google-cloud-networking-observability

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈122 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈10k more on demand in 9 files.

Description uses 6.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈487 characters, or 6.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Google Cloud Networking Observability Expert

Usage Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution.

🛑 Core Directive: Results First

  1. Single-Guide Loading: Identify the matching guide in Section 2 and read only that file before acting (plus references/mcp-usage.md when MCP tools are available in your environment).
  2. Data & Metric Lookups: Execute targeted queries to retrieve the requested data. Once obtained (including 0, null, or "No traffic"), present it and stop immediately. Never query a second source (e.g., comparing BigQuery and Monitoring) to double-check a conclusive answer.
  3. Troubleshooting & Root-Cause Analysis: Follow the matching guide's workflow to inspect control-plane configurations, logs, and metrics before forming conclusions. Recommend fixes with exact resource names and commands—never mutate project resources or workload state during investigation (except ephemeral Connectivity Tests when path verification is needed).

Procedures

1. Environment & Source Rules

  • Prerequisites: Target projects require an active billing account, authenticated SDK access (gcloud auth login or GOOGLE_APPLICATION_CREDENTIALS, gcloud config set project {project_id}, default region e.g. us-central1 via gcloud config set compute/region {region}; see Google Cloud CLI installation and locations — never install tools without explicit user approval), enabled APIs (compute.googleapis.com, logging.googleapis.com, monitoring.googleapis.com, bigquery.googleapis.com, networkmanagement.googleapis.com), and read roles (roles/compute.networkViewer, roles/logging.viewer, roles/monitoring.viewer, roles/bigquery.jobUser, roles/bigquery.dataViewer, or roles/networkmanagement.admin for Connectivity Tests).
  • BigQuery First for Volume/Top-N: Always prefer BigQuery linked datasets (_AllLogs) over Cloud Logging for volume trends, top talkers, or aggregations. Never manually aggregate time-series points via the Monitoring API for Top-N tasks.
  • Schema & Sample Check: Inspect a sample log record (LIMIT 1 / --limit=1 --format=json) or fetch the guide's official .md.txt documentation URL before writing complex filters or aggregations to verify exact payload field paths; if bq query fails with schema errors, run bq show --schema --format=json {project}:{dataset}.{table} and bq query --use_legacy_sql=false --dry_run.
  • Metadata Fallback: Subnets with EXCLUDE_ALL_METADATA have NULL VM names in VPC Flow Logs; filter or group by internal IP (jsonPayload.connection.src_ip) instead.
  • Tool Priority: Prefer MCP servers (references/mcp-usage.md) when declared in your tools; otherwise use gcloud/bq. Never use gcloud monitoring; use REST curl templates in references/metrics-analysis.md.

2. Analysis Guides (Read Only the Single Matching Guide)

Symptom or Task Reference Guide
VPC Flow Logs: traffic volume, top talkers, latency, packet drops and loss rates, Private Service Connect (PSC / PSC-I), serverless workloads references/vpc-flow-analysis.md
VPC Flow Logs Cost Estimation references/vpc-flow-logs-cost-estimation.md
Firewall Rules & Logs: DENY/ALLOW hits, attributing firewall deny drops to specific rules, blocked IPs, rule shadowing references/firewall-analysis.md
Cloud NAT: gateway discovery, NAT IP/port mapping audit, port exhaustion drops, allocated connection counts references/cloud-nat-analysis.md
Threat Logs: Cloud IDS / Firewall Plus high-severity alerts and top attackers references/threat-analysis.md
Metrics & VPN: internal/external RTT, VM throughput, packet loss, or Cloud VPN (vpn_gateway health, traffic, drops) references/metrics-analysis.md
Connectivity Tests: reachability path create, describe, delete references/connectivity-tests.md

Boundaries (CRITICAL)

  • Print SQL: Always print generated SQL in the response.
  • Flow Analyzer Link: For VPC Flow Log tasks, include Google Cloud Console Flow Analyzer.
  • First-Turn Time Math: Compute relative time ranges (e.g., "12 hours ago") in the first turn.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides diagnostic tools for Google Cloud networking by analyzing logs and metrics. It utilizes official Google Cloud CLI tools and APIs to perform observability tasks and includes logical safeguards for data processing.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: CRITICAL · 2 issues

Signed by skilld at 5fb62c2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago
metadata
{
  "version": "1.0.8",
  "category": "Compute"
}

README badge

README badge for google/skills/google-cloud-networking-observability