Database Observability
grafana/skills
Set up Grafana Cloud Database Observability for MySQL and PostgreSQL — enables pgstatstatements / Performance Schema, creates a least-privilege monitoring user, configures the…
Debug SQL execution time via distributed tracing (OpenTelemetry / Tempo).
Install Mz Query Tracing
$ npx skills add MaterializeInc/materialize --skill mz-query-tracing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-query-tracing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MaterializeInc/materialize.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/mz-query-tracing .claude/skills/mz-query-tracing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mz-query-tracing" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracing into .claude/skills/mz-query-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-query-tracing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MaterializeInc/materialize --skill mz-query-tracing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-query-tracing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MaterializeInc/materialize.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/mz-query-tracing .agents/skills/mz-query-tracing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mz-query-tracing" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracing into .agents/skills/mz-query-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-query-tracing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MaterializeInc/materialize --skill mz-query-tracing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-query-tracing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MaterializeInc/materialize.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/mz-query-tracing .cursor/skills/mz-query-tracing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mz-query-tracing" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracing into .cursor/skills/mz-query-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-query-tracing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MaterializeInc/materialize.git --path .agents/skills/mz-query-tracing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MaterializeInc/materialize --skill mz-query-tracing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-query-tracing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MaterializeInc/materialize.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/mz-query-tracing .gemini/skills/mz-query-tracing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mz-query-tracing" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracing into .gemini/skills/mz-query-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-query-tracing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MaterializeInc/materialize mz-query-tracingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MaterializeInc/materialize --skill mz-query-tracing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MaterializeInc/materialize.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/mz-query-tracing .github/skills/mz-query-tracing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mz-query-tracing" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracing into .github/skills/mz-query-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-query-tracing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MaterializeInc/materialize --skill mz-query-tracing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MaterializeInc/materialize mz-query-tracing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MaterializeInc/materialize.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/mz-query-tracing .opencode/skills/mz-query-tracing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mz-query-tracing" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-query-tracing into .opencode/skills/mz-query-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-query-tracing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mz-query-tracing- GitHub stars
- 6.4k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 708 words
- Files
- 2
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Debug SQL execution time via distributed tracing (OpenTelemetry / Tempo).
- Works in 8 steps: Start the monitoring stack → Start environmentd with tracing → Verify both services are running → …
- Tasks that involve Observability
- SKILL.md covers Important: Use Optimized Builds, Prerequisites, Workflow: Trace a Query and Interpreting Results, plus 1 more section
- Runs Python scripts from its folder; calls curl, psql and python3
What it does
Mz Query Tracing is an agent skill from MaterializeInc/materialize. Debug SQL execution time via distributed tracing (OpenTelemetry / Tempo). Trigger: "why is this query slow", "where is the time going", "this SELECT takes forever", or latency breakdown for SQL statement. Also tracing queries, span analysis, Tempo traces, trace IDs, opentelemetryfilter.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `trace_tree.py`).
It sits in DevOps & Cloud, covering Observability and SQL. It works with SQL, OpenTelemetry and PostgreSQL. The repository describes itself as: The live data layer for apps and AI agents. Create up-to-the-second views into your business, just using SQL.
When your agent uses it
- Tasks that involve Observability
- Tasks that involve SQL
Example prompts
- “why is this query slow”
- “where is the time going”
- “this SELECT takes forever”
- “/mz-query-tracing”
Requirements
- Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
- Start the monitoring stack
- Start environmentd with tracing
- Verify both services are running
- Set the trace filter at runtime (if not set at startup)
- Run the query and capture the trace ID
- Wait for spans to be flushed
- Fetch the trace from Tempo
- Analyze the trace
What it can do on your machine
Read from SKILL.md and the folder at commit b760ecc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
curlpsqlpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mz Query Tracing loads about 1.8k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 708 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 708 words (~1,842 tokens).
“Use distributed tracing (OpenTelemetry / Tempo) to understand where time is spent during SQL statement execution in a local Materialize instance.”
- name
- mz-query-tracing
Files
SKILL.md and 1 other file in .agents/skills/mz-query-tracing of MaterializeInc/materialize.
- SKILL.md
- trace_tree.py
Open the folder on GitHubat commit b760ecc
Compare with similar skills
Mz Query Tracing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mz Query Tracing this skillMaterializeInc/materialize | 6.4k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Database Observabilitygrafana/skills | 279 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| TMA1 Observability Querytma1-ai/tma1 | 119 | — | ~5.1k | Automated safety check: Notes | Apache-2.0 | |
| Rift Backend EffectCompound-inc/rift | 124 | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Gorm ExpertLeoYeAI/openclaw-master-skills | 2.2k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Otel Javaollygarden/opentelemetry-agent-skills | 106 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
TMA1 Observability Query
tma1-ai/tma1
Answers questions about agent spend, token use, traces, events, errors and tool usage by running read-only SQL against a local TMA1 observability store.
Rift Backend Effect
Compound-inc/rift
A skill your agent uses when adding, reviewing, or refactoring backend code in Rift's TanStack Start app that should follow apps/start/BACKENDEFFECTPLAYBOOK.md.
Gorm Expert
LeoYeAI/openclaw-master-skills
GORM v2 最佳实践与性能优化。适用于：代码审查、慢查询优化、N+1、连接池、 事务管理、分库分表、Prometheus/OTel监控、Session安全、Clause/Upsert、 缓存集成、BaseModel脚手架、SQL→struct生成、多租户隔离。
Otel Java
ollygarden/opentelemetry-agent-skills
OpenTelemetry in Java — Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management, sensitive-data capture and…
GCP Essentials
ericrisco/rsc-harness
A skill your agent uses when running a small product on core Google Cloud via the gcloud CLI: a project, Cloud Run deploys, a locked-down Cloud Storage bucket, managed Cloud SQL, and least-privilege…
More from MaterializeInc/materialize
All 15 skills in this repoMz Release Signoff
MaterializeInc/materialize
Verify a release candidate on the Grafana dashboards and sign off in release.
Mz Benchmark
MaterializeInc/materialize
Add/modify/debug Materialize perf benchmark scenarios. An agent skill from MaterializeInc/materialize.
Mz Commit
MaterializeInc/materialize
Trigger: "commit", "prepare commit", "create PR", "push", "open pull request", or mentions committing, pre-commit checks, pull requests in Materialize.
Mz Dbt Release
MaterializeInc/materialize
Cut a dbt-materialize PyPI release: bump the version in version.py and setup.py, date the Unreleased CHANGELOG entry, and open the release PR with a Ship: <url body.
Mz Debug CI
MaterializeInc/materialize
Investigate CI failures on PR via gh + Buildkite MCP or bk CLI.
Mz Limits Test
MaterializeInc/materialize
Add/modify/debug limits test. An agent skill from MaterializeInc/materialize.
Related
Works with
Categories
Questions about Mz Query Tracing
What does Mz Query Tracing do?
Debug SQL execution time via distributed tracing (OpenTelemetry / Tempo). Mz Query Tracing is an agent skill from MaterializeInc/materialize. Debug SQL execution time via distributed tracing (OpenTelemetry / Tempo).
When should I use Mz Query Tracing?
Mz Query Tracing fits situations like: tasks that involve Observability; tasks that involve SQL.
How do I install Mz Query Tracing in Claude Code?
Run `npx skills add MaterializeInc/materialize --skill mz-query-tracing -a claude-code`. Or copy the skill folder (.agents/skills/mz-query-tracing in MaterializeInc/materialize) into .claude/skills/mz-query-tracing in your project. Claude Code loads it when a task matches its description.
How do I install Mz Query Tracing in Codex?
Run `npx skills add MaterializeInc/materialize --skill mz-query-tracing -a codex`. Or copy the skill folder (.agents/skills/mz-query-tracing in MaterializeInc/materialize) into .agents/skills/mz-query-tracing in your project. Codex loads it when a task matches its description.
Can I use Mz Query Tracing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MaterializeInc/materialize --skill mz-query-tracing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mz-query-tracing, .gemini/skills/mz-query-tracing, .github/skills/mz-query-tracing and .opencode/skills/mz-query-tracing in your project.
What does Mz Query Tracing need to run?
Going by SKILL.md and its folder, Mz Query Tracing needs Python for the scripts in its folder and the command-line tools its instructions call (curl, psql and python3). Our summary lists: Python 3.
Does Mz Query Tracing access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Mz Query Tracing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mz Query Tracing use?
Mz Query Tracing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Mz Query Tracing use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mz Query Tracing?
Skills that share tags, products or a category with Mz Query Tracing: Database Observability (grafana/skills, 279 stars), TMA1 Observability Query (tma1-ai/tma1, 119 stars), Rift Backend Effect (Compound-inc/rift, 124 stars) and Gorm Expert (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mz Query Tracing?
MaterializeInc (a GitHub organization) maintains it in MaterializeInc/materialize, which has 6,377 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.
Source: MaterializeInc/materialize on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.