Download for MacApple silicon, macOS 14+
Skill

logfire-query

@pydantic Updated 2026-10-16

Query and analyze Logfire telemetry data — traces, logs, spans, metrics, summaries, and SQL results. Use this skill when the user asks to "query logfire", "search traces", "find logs", "query data", "search spans", "look up errors in logfire", "get metrics from logfire", "analyze telemetry", "summarize errors", "find root cause", or add Logfire querying capabilities to code. Do not use this skill for direct Logfire UI, browser, live-view, Explore-page, or link-opening requests; use logfire-ui instead. If "show" or "view" wording is ambiguous, ask whether the user wants a UI view or query analysis.

Install

With your agent

Install OMGSkills skill "pydantic/skills:logfire-query" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/pydantic/skills /tmp/skills && ln -s /tmp/skills/skills/logfire-query ~/.claude/skills/logfire-query

From README

Query Logfire Data When to Use This Skill Invoke this skill when: User wants to query traces, logs, spans, or metrics from Logfire User wants to search for specific events, errors, or patterns in telemetry data User wants to analyze OpenTelemetry data stored in Logfire User wants to add programmatic query capabilities to their code User asks to "query logfire", "search traces", "find logs", "get metrics", "count", "summarize", "compare", or "find root cause" User-Facing Progress Keep progress updates terse. Do not narrate route classification, local skill instructions, schema selection, or routine query . If an update is needed, use one short sentence focused on the action, such as "Querying recent Logfire errors." Critical Routing: One Workflow Per Request Before using any query tool, classify the request. Query route: "analyze", "query", "count", "summarize", "compare", "find root cause", "find slowest", "look up errors", "get metrics", or "add query capabilities".