Agent skill · data analytics · google

cloud-logging-query-generation

Generates Logging Query Language (LQL) queries for Cloud Logging on Google Cloud from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google Cloud service. Don't use this skill to query other databases, such as SQL or Cloud Spanner.

Why this skill is useful

Provides specific syntax rules and query generation patterns for Google Cloud Logging that the AI wouldn't reliably generate on its own.

What it needs

About 4k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

Generate Logging Query Language queries Use this skill to generate correct Logging Query Language (LQL) queries for Cloud Logging. 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-query-generation)" and append agent-skills/1.0 (skill:cloud-logging-query-generation) to User-Agent headers. Core rules 1. Strict syntax requirements: Always use double quotes (") for string literals. Do not use single quotes ('). Write boolean operators in all capitals: AND, OR, NOT. Always use parentheses to group terms and explicitly enforce precedence. 2. Common pitfalls: Instance ID vs. Instance Name: For the gceinstance resource type, do NOT compare instance names to instance IDs. Instance names are strings (for example, my-instance). Instance IDs are numeric. If you only have the name, then search by instance name, SEARCH("my-instance"), or use resource.labels.instancename if that label is available for the resource. Resource Type Accuracy: Do not guess resource types. You must look up the correct resource.type value in the service-specific reference files. For example, use internalhttplbrule for Internal HTTP(S) Load Balancer rules when filtering by forwarding rule name or region (instead of httploadbalancer). 3. Output format and placeholders: Output only the raw LQL query text. Do not include conversational filler. Do not wrap the query in markdown code blocks unless explicitly requested by the user. Valid LQL comments (using --) are allowed, and are the ONLY acceptable way to include explanations or warnings. Never block on missing variables. If the user's request lacks specific identifiers (like a project ID, instance name, or IP address), do not ask them for clarification. …

How to use it

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

@skills google/cloud-logging-query-generation

View the source on GitHub

Browse the @skills marketplace