Skip to main content
skill CX Codex

gcloud-usage — Claude Code skill for GCP logs

gcloud-usage is a Claude Code skill that guides Google Cloud log queries and analysis of metrics, traces, and alerts. It supports production debugging and GCP observability work.

Apache-2.0 ★ 1,216 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install gcloud-tools@claude-settings
Open on GitHub

What gcloud-usage does

The skill covers Google Cloud observability workflows: filtering Cloud Logging entries by severity, resource, time, and JSON fields, then choosing whether metrics, logs, or traces are the right evidence. Its debugging sequence starts with metrics, moves to logs around the incident, and follows requests through traces.

Alert guidance covers error rates, latency, and resource pressure. The skill also discusses reducing log costs through exclusion filters, sampling, shorter retention, and routing logs to cheaper storage. For most metrics, it recommends alert windows of 5–15 minutes, so thresholds and windows need to match the service being monitored.

It is meant for questions about GCloud logs, Google Cloud metrics, trace analysis, and GCP production debugging. Examples use fields such as jsonPayload.user_id and resources such as cloud_run_revision, which can help shape queries for a specific service.

What it helps with

  • filter Cloud Logging entries by severity and service
  • search logs by timestamp or JSON field
  • trace a production issue across metrics, logs, and traces
  • set alerts for elevated errors or latency
  • cut log volume with exclusion filters

Example prompts for the agent

  • Find high-severity Cloud Logging entries for the api service.
  • Help me compare metrics, logs, and traces for a failed request.
  • Draft a Cloud Logging filter that excludes /health checks.

How to install gcloud-usage

1Plugin marketplace

/plugin marketplace add fcakyon/claude-codex-settings
/plugin install gcloud-tools@claude-settings

This installs the whole gcloud-tools plugin with all its skills

2Skills CLI (Vercel)

npx skills add fcakyon/claude-codex-settings --skill gcloud-usage -a claude-code

3Manually: put the files in place

~/.claude/skills/gcloud-usage/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/gcloud-usage/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about gcloud-usage

How do I install gcloud-usage in Claude Code?

In Claude Code, add the marketplace with /plugin marketplace add fcakyon/claude-codex-settings, then install the plugin with /plugin install gcloud-tools@claude-settings.

What does gcloud-usage do?

It provides guidance for querying Cloud Logging, interpreting metrics and traces, designing alerts, and managing log costs.

How does the skill suggest debugging a GCP incident?

Start with metrics to locate when the issue began, inspect logs from that period, then follow requests in traces. It also recommends checking resource logs.

Source text

SKILL.md · Apache-2.0
---
name: gcloud-usage
description: This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
---

# GCP Observability Best Practices

## Structured Logging

### JSON Log Format

Use structured JSON logging for better queryability:

```json
{
  "severity": "ERROR",
  "message": "Payment failed",
  "httpRequest": { "requestMethod": "POST", "requestUrl": "/api/payment" },
  "labels": { "user_id": "123", "transaction_id": "abc" },
  "timestamp": "2025-01-15T10:30:00Z"
}
```

### Severity Levels

Use appropriate severity for filtering:

- **DEBUG:** Detailed diagnostic info
- **INFO:** Normal operations, milestones
- **NOTICE:** Normal but significant events
- **WARNING:** Potential issues, degraded performance
- **ERROR:** Failures that don't stop the service
- **CRITICAL:** Failures requiring immediate action
- **ALERT:** Person must take action immediately
- **EMERGENCY:** System is unusable

## Log Filtering Queries

### Common Filters

```
# By severity
severity >= WARNING

# By resource
resource.type="cloud_run_revision"
resource.labels.service_name="my-service"

# By time
timestamp >= "2025-01-15T00:00:00Z"

# By text content
textPayload =~ "error.*timeout"

# By JSON field
jsonPayload.user_id = "123"

# Combined
severity >= ERROR AND resource.labels.service_name="api"
```

### Advanced Queries

```
# Regex matching
textPayload =~ "status=[45][0-9]{2}"

# Substring search
textPayload : "connection refused"

# Multiple values
severity = (ERROR OR CRITICAL)
```

## Metrics vs Logs vs Traces

### When to Use Each

**Metrics:** Aggregated numeric data over time

- Request counts, latency percentiles
- Resource utilization (CPU, memory)
- Business KPIs (orders/minute)

**Logs:** Detailed event records

- Error details and stack traces
- Audit trails
- Debugging specific requests

**Traces:** Request flow across services

- Latency breakdown by service
- Identifying bottlenecks
- Distributed system debugging

## Alert Policy Design

### Alert Best Practices

- **Avoid alert fatigue:** Only alert on actionable issues
- **Use multi-condition alerts:** Reduce noise from transient spikes
- **Set appropriate windows:** 5-15 min for most metrics
- **Include runbook links:** Help responders act quickly

### Common Alert Patterns

**Error rate:**

- Condition: Error rate > 1% for 5 minutes
- Good for: Service health monitoring

**Latency:**

- Condition: P99 latency > 2s for 10 minutes
- Good for: Performance degradation detection

**Resource exhaustion:**

- Condition: Memory > 90% for 5 minutes
- Good for: Capacity planning triggers

## Cost Optimization

### Reducing Log Costs

- **Exclusion filters:** Drop verbose logs at ingestion
- **Sampling:** Log only percentage of high-volume events
- **Shorter retention:** Reduce default 30-day retention
- **Downgrade logs:** Route to cheaper storage buckets

### Exclusion Filter Examples

```
# Exclude health checks
resource.type="cloud_run_revision" AND httpRequest.requestUrl="/health"

# Exclude debug logs in production
severity = DEBUG
```

## Debugging Workflow

1. **Start with metrics:** Identify when issues started
2. **Correlate with logs:** Filter logs around problem time
3. **Use traces:** Follow specific requests across services
4. **Check resource logs:** Look for infrastructure issues
5. **Compare baselines:** Check against known-good periods

© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings

Similar skills

All skills for Cloud: AWS, Azure, GCP →

From the same set113

The whole set →
start-environment start-environment teaches the assistant how to spin up local development containers via dev docker up, wait for healthchecks, and inspect ports. CX Codex +1 ★ 1,216repo stars service-architecture The service-architecture rule maps Polar’s shared Docker infrastructure and per-worktree app stacks. Use it to understand service addresses, container dependencies, and network boundaries. CX Codex +1 ★ 1,216repo stars openship-config Inspects a repository and builds openship.json with only the overrides OpenShip needs. Use it before a first deploy or when openship config validate fails. CX Codex +1 ★ 1,216repo stars app-auth The app-auth skill for Claude Code structures and implements application authentication flows. It activates when handling social login, password recovery, account switching, or sign-in components. CX Codex +1 ★ 1,216repo stars dokploy-deploy dokploy-deploy hands the agent Dokploy's own docs: cloud and self-hosted setup, app and Compose deploys, databases, domains, plus a CLI command index. CX Codex +1 ★ 1,216repo stars pr-reviewer The pr-reviewer subagent for Claude Code inspects GitHub pull requests for security flaws and breaking bugs using the gh CLI, without cluttering reviews. CX Codex ★ 1,216repo stars seo-audit The seo-audit skill for Claude Code and Codex audits pages for search visibility and investigates ranking problems. It checks crawl and index signals, page elements, content, and the order of follow-up checks. CX Codex +1 ★ 1,216repo stars review-overleaf review-overleaf — a skill for Claude Code and Codex that pulls unresolved reviewer comments from an Overleaf project, locates each in your local LaTeX repository, and proposes edits. CX Codex +1 ★ 1,216repo stars

Project sponsors

Companies that keep this analytics open