Download for MacApple silicon, macOS 14+
Skill

firetiger-query

@firetiger-oss Updated 2026-07-08

Use when querying Firetiger telemetry with SQL — finding traces, searching logs, inspecting metrics, locating errors or slow requests, computing latency percentiles, aggregating observability data, or querying a connected source (Postgres, MySQL, ClickHouse, Datadog, Prometheus, GCP Monitoring) through the Firetiger MCP `query` tool. Always use this skill before writing a Firetiger query — it carries the critical gotchas (slashed table names must be quoted, duration is computed not stored, status codes are integers, attributes are structs not maps, fully-qualify "connections/{name}".table to reach a connected source) that make queries succeed.

Install

With your agent

Install OMGSkills skill "firetiger-oss/claude-plugin:skills/firetiger-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/firetiger-oss/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/firetiger-query ~/.claude/skills/firetiger-query

From README

Firetiger Query Firetiger stores telemetry in Apache Iceberg tables with dynamic schema inference. Run DuckDB SQL against it with the Firetiger MCP server's query tool (parameter: sql). Key gotcha: the query tool auto-injects USE "connections/iceberg-gateway", so you reference tables by their quoted name ("opentelemetry/traces/checkout-service") — you don't prefix a catalog path. There is no enforced row cap, but the tool returns every row as JSON, so always add a LIMIT (and explicit columns, not SELECT ) to avoid dumping huge nested rows. Table naming Tables are namespaced by signal type and service name. Names with slashes must be double-quoted. The {servicename} layout is the default shard key; a deployment can configure a different one, so always SHOW TABLES; to see the real names.