Railway's official agent skill: create projects, provision databases and buckets, deploy, manage variables and domains, and read build failures back — from the CLI, API or MCP server.
Grafana Tempo & TraceQLSkill
Summary
Grafana's official Tempo skill: stand up a tracing backend that needs nothing but object storage, then write TraceQL that finds the slow span instead of scrolling for it.
Features
- Local Tempo bring-up with OTLP push and ingestion verified by metric and trace fetch
- TraceQL reference: span/resource/event scopes, intrinsics, structural operators >> and <<
- TraceQL metrics with rate() and quantile_over_time, plus the /api/search curl equivalent
- Grafana Alloy OTLP receiver-to-exporter config for application instrumentation
- tempo-distributed Helm deployment against S3, GCS or Azure block storage
- Multi-tenant X-Scope-OrgID setup and the mismatch that hides traces in Explore
Install This Skill
Add this skill to your favorite AI agent in a few steps.
Skill Content
Description
Tempo is Grafana's distributed tracing backend, and its selling point is what it does not need: no Cassandra, no Elasticsearch, no index cluster. Traces go into Parquet blocks in S3, GCS or Azure, and that is the whole storage tier. This skill is the official Grafana Labs guidance for running it and querying it.
It is built around workflows rather than a feature tour. The first one stands Tempo up locally from the upstream Docker Compose example, pushes a synthetic OTLP span with a copy-pasteable curl, and — importantly — verifies the span actually landed by checking tempo_distributor_spans_received_total and fetching the trace back by ID. The second wires a real application in through Grafana Alloy, with the otelcol.receiver.otlp → otelcol.exporter.otlp config and the exporter metric to confirm spans are leaving. The fourth deploys the tempo-distributed Helm chart against an S3 bucket and checks every component pod is Ready before port-forwarding the query frontend.
The third workflow is TraceQL. The skill covers the scopes that matter (span., resource., event.), intrinsics such as duration, kind and status, the structural operators >> and << that let you ask "which server span had a downstream error", and the metrics functions rate() and quantile_over_time for turning a trace search into a time series. A curl example shows the same query through /api/search for anything scripted.
Ingestion covers OTLP, Jaeger, Zipkin, OpenCensus and Kafka. Multi-tenancy via X-Scope-OrgID is documented alongside the mismatch that causes the single most common complaint — traces are being written but Explore shows nothing because the writer and the datasource disagree on the tenant header. Other troubleshooting entries cover a 503 on /ready, 429s on push and the levers for a slow TraceQL query.
Apache-2.0, shipped in grafana/skills, and installable via npx skills add grafana/skills or the Claude Code plugin marketplace. Companion references go deeper on the full TraceQL cheat sheet and on architecture, ports, tuning, the metrics-generator for RED span metrics and service graphs, and the traces-to-logs / metrics / profiles datasource links.
Related Skills
Diagnoses wrong gradients in differentiable NVIDIA Warp programs by measuring first — comparing autodiff against finite differences on a shrunk reproduction before proposing any fix.
Google's official skill for the gws CLI — drive Gmail, Drive, Calendar, Sheets, Docs, Chat and Admin APIs from an agent, with Model Armor screening.
Netlify's official skill for zero-config managed Postgres — querying from Functions, Drizzle setup, migrations and per-preview database branches.