Agent skill · data analytics · google

cloud-logging-cross-project-configuration

Configure and troubleshoot Google Cloud cross-project centralized logging and read-time aggregation. Use when: - Setting up log routing from multiple projects/folders/organizations to a central log bucket. - Creating cross-project log sinks and configuring central log buckets. - Troubleshooting cross-project routing. Don't use for single-project basic configurations.

Why this skill is useful

Provides specific `gcloud` commands and configurations for centralized logging across multiple Google Cloud projects that the AI wouldn't reliably generate on its own.

What it needs

Requires google-cloud account access. About 9k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

Configuring Cross-Project Logging This skill describes how to use gcloud commands to configure Cloud Logging so that you store log data in a central location, regardless of the point of origin. The skill also describes how to query log data when that data is stored in multiple projects. [!IMPORTANT] Sandbox Network Limitation (CRITICAL for Agent Testing): During evaluation or in restricted sandboxed environments, network traffic to GCP APIs is blocked. Do NOT run network discovery commands to find resource names, project IDs, or organization IDs. Always use the exact project IDs or placeholders provided in the user prompt or instructions, for example, {projectid}, {sourceprojectid}, {centralprojectid}. Assume these resources exist and proceed directly with configuration commands. Running these discovery commands will cause the execution to hang and timeout. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:cloud-logging-cross-project-configuration)" and append agent-skills/1.0 (skill:cloud-logging-cross-project-configuration) to User-Agent headers. Safety and Confirmation Tiers (CRITICAL) Before executing any commands on behalf of the user, you MUST adhere to the following safety tiers based on the action requested: 1. Tier R: Read-Only Description: Commands that only read state or query logs. Example commands: gcloud logging read gcloud logging buckets list Rule: No confirmation needed. You may execute these commands immediately to gather information. 2. Tier M: Mutation (Non-Billing) Description: Configuration modifications or free metadata creations that do not incur direct storage or billing costs and do not affect resource security/access policies. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/cloud-logging-cross-project-configuration

View the source on GitHub

Browse the @skills marketplace