cloud-logging-query-generation

Generates Logging Query Language queries for Google Cloud Logging from natural language.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/oliverconstance/webapp-scrum-team --skill cloud-logging-query-generation-oliverconstance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-logging-query-generation
Source: https://github.com/oliverconstance/webapp-scrum-team/tree/main/.agent/skills/cloud-logging-query-generation
Command: npx skills add https://github.com/oliverconstance/webapp-scrum-team --skill cloud-logging-query-generation-oliverconstance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing correct Logging Query Language (LQL) queries for Google Cloud Logging requires knowing exact syntax rules, service-specific resource types, and field schemas, which slows down debugging and log analysis. ## Core Features & Use Cases - Natural language to LQL conversion: Translates plain-English log requests into syntactically valid LQL queries with correct quoting, boolean operators, and grouping. - Service-specific accuracy: Consults reference files for over 20 Google Cloud services (GCE, GKE, Cloud Run, BigQuery, Cloud SQL, and more) to use the correct resource.type and field schemas. - Safe handling of unknowns: Falls back to global SEARCH() queries with explanatory LQL comments when schemas are unknown, and inserts placeholder values instead of blocking on missing identifiers. - Use Case: While debugging a production issue on Cloud Run, ask for recent error logs and receive a ready-to-paste LQL query filtered by the correct resource type and severity. ## Quick Start Ask the agent to generate a Cloud Logging query that shows all error logs from my Cloud Run service in the last hour.

Frequently Asked Questions about cloud-logging-query-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Cloud Logging query from natural language?▼

Describe the logs you want in plain English, such as errors from a specific service, and the skill generates a valid Logging Query Language query. It enforces double quotes, uppercase boolean operators, and explicit parentheses for precedence.

How do I filter Google Cloud logs by a specific service?▼

The skill reads service-specific reference files for over 20 Google Cloud services to select the correct resource.type and field schemas. For example, it uses internal_http_lb_rule for Internal HTTP(S) Load Balancer rules instead of guessing.

Can I query Cloud Logging audit logs for who created or deleted a resource?▼

Yes, audit log queries use protoPayload.methodName with the colon operator for substring matching, such as protoPayload.methodName:"compute.instances.insert". Generic API enable or disable events use resource.type="audited_resource".

What happens if my request is missing a project ID or instance name?▼

The skill never blocks on missing identifiers. It inserts uppercase placeholder strings wrapped in angle brackets, such as "<PROJECT_ID>", directly into the query so you can fill them in later.

When should I not use Logging Query Language generation?▼

Do not use this skill to query other databases such as SQL or Spanner data. It is scoped strictly to Google Cloud Logging log data and does not handle general-purpose database querying.