Agent skill · data analytics · google
cloud-logging-configuration-basics
Configure single-project Cloud Logging on Google Cloud: regional log buckets, log sinks, log views, restricting or hiding sensitive logs in the default view (_Default) filter, IAM permissions for views (Logs View Accessor, IAM conditions), logs-based metrics, log exclusions, and sampling. Don't use for cross-project logging or multi-project setups.
Why this skill is useful
Provides specific commands and configurations for Google Cloud Logging that the AI wouldn't reliably generate on its own.
What it needs
Requires google-cloud-sdk installed locally. Requires google-cloud account access. About 7k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
Configuring Cloud Logging Use this skill to configure Cloud Logging resources such as log buckets, log views, or log sinks. [!IMPORTANT] Sandbox Network Limitation (CRITICAL for Agent Testing): During evaluation or in restricted sandboxed environments, network traffic to Google Cloud 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}. 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-configuration-basics)" and append agent-skills/1.0 (skill:cloud-logging-configuration-basics) 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. Example commands: gcloud logging views create gcloud logging views update gcloud logging scopes create gcloud logging buckets create Rule: No confirmation needed. You may execute these commands immediately to apply configurations. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/cloud-logging-configuration-basics