workspace/skills/gcp-cloud-monitoring/SKILL.md
Google Cloud Monitoring — time series metrics, alert policies, active alerts, metric discovery. Use when checking GCP network performance, investigating firing alerts, querying VM CPU or memory metrics, reviewing Cloud VPN tunnel status, or assessing load balancer latency.
npx skillsauth add automateyournetwork/netclaw gcp-cloud-monitoringInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
https://monitoring.googleapis.com/mcp (Streamable HTTP)GOOGLE_APPLICATION_CREDENTIALS) or gcloud auth application-default loginGCP_PROJECT_ID environment variable| Tool | What It Does |
|------|-------------|
| list_timeseries | Query time series data — CPU, memory, network, disk metrics for any GCP resource |
| list_metric_descriptors | Discover available metric types in a project — find what you can monitor |
| list_alert_policies | List all alerting policies — conditions, notification channels, thresholds |
| get_alert_policy | Get details of a specific alerting policy |
| list_alerts | List current and past alert violations — what's firing right now |
| get_alert | Get details of a specific alert violation |
When a user asks "how is our GCP network performing?":
list_alerts to find any active alert violationslist_timeseries for compute.googleapis.com/instance/network/received_bytes_count and sent_bytes_countlist_timeseries for compute.googleapis.com/instance/network/received_packets_dropped_countlist_timeseries for compute.googleapis.com/firewall/dropped_packets_countlist_timeseries for loadbalancing.googleapis.com/https/request_count and total_latenciesWhen investigating GCP alerts:
list_alerts — find what's currently firingget_alert — condition, threshold, resource affectedget_alert_policy — what triggers this alert, notification channelslist_timeseries for the affected metric — see the spike/anomalygcp-cloud-logging for correlated log entriesWhen checking GCP infrastructure health:
list_metric_descriptors filtered by service (compute, networking, loadbalancing)list_timeseries for compute.googleapis.com/instance/cpu/utilization and memory metricslist_timeseries for compute.googleapis.com/instance/disk/read_bytes_count and write metricslist_timeseries for network sent/received byteslist_alert_policies + list_alerts — any policies in violation?| Metric | What It Tells You |
|--------|-------------------|
| compute.googleapis.com/instance/network/received_bytes_count | Inbound network throughput per VM |
| compute.googleapis.com/instance/network/sent_bytes_count | Outbound network throughput per VM |
| compute.googleapis.com/instance/network/received_packets_dropped_count | Dropped inbound packets (congestion) |
| compute.googleapis.com/instance/network/sent_packets_dropped_count | Dropped outbound packets (congestion) |
| compute.googleapis.com/firewall/dropped_packets_count | Packets dropped by VPC firewall rules |
| loadbalancing.googleapis.com/https/request_count | HTTP(S) LB request rate |
| loadbalancing.googleapis.com/https/total_latencies | HTTP(S) LB end-to-end latency |
| loadbalancing.googleapis.com/https/backend_latencies | Backend response time behind LB |
| vpn.googleapis.com/tunnel_established | Cloud VPN tunnel state (1=up, 0=down) |
| vpn.googleapis.com/sent_bytes_count | Bytes sent through VPN tunnel |
| router.googleapis.com/bgp/received_routes_count | BGP routes received by Cloud Router |
| interconnect.googleapis.com/link/received_bytes_count | Cloud Interconnect link throughput |
GCP_PROJECT_ID — Google Cloud project IDGOOGLE_APPLICATION_CREDENTIALS — Path to service account key JSON filetesting
Human-in-the-loop escalation via HumanRail — route low-confidence agent decisions, pre-destructive operation approvals, and ambiguous incident tickets to real human engineers. Human answers are verified and returned as structured output. Workers are paid via Lightning Network. Use when the agent is uncertain, when a destructive change needs explicit human sign-off beyond a ServiceNow CR, or when an ambiguous ticket requires human triage before automated handling.
testing
Manage EVE-NG node lifecycle. Use when listing nodes, checking runtime state, creating or deleting nodes, starting or stopping nodes or whole labs, verifying node details, or wiping node NVRAM back to factory defaults.
development
Manage EVE-NG labs and platform inventory. Use when listing labs, checking lab metadata, creating or deleting labs, importing or exporting lab archives, checking EVE-NG health or auth, or verifying available node images before build work.
tools
Execute live CLI commands on running EVE-NG nodes over telnet console. Use when running show commands, making live config changes, verifying protocol state, testing connectivity, checking console readiness, or interacting with IOS, Junos, VPCS, EOS, or NX-OS nodes.