Debugging Opik E2E Tests
comet-ml/opik
Investigates a failed Opik end-to-end test from CI, TestOps or a local run, decides regression versus flake, and proposes a fix without editing tests.
Investigate CI failures on PR via gh + Buildkite MCP or bk CLI.
Install Mz Debug CI
$ npx skills add MaterializeInc/materialize --skill mz-debug-ci -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-debug-ci --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-debug-ci .claude/skills/mz-debug-ci && 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-debug-ci" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-debug-ci into .claude/skills/mz-debug-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-debug-ci", 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-debug-ciType 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-debug-ci -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-debug-ci --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-debug-ci .agents/skills/mz-debug-ci && 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-debug-ci" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-debug-ci into .agents/skills/mz-debug-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-debug-ci", 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-debug-ci -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-debug-ci --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-debug-ci .cursor/skills/mz-debug-ci && 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-debug-ci" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-debug-ci into .cursor/skills/mz-debug-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-debug-ci", 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-debug-ci--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-debug-ci -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-debug-ci --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-debug-ci .gemini/skills/mz-debug-ci && 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-debug-ci" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-debug-ci into .gemini/skills/mz-debug-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-debug-ci", 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-debug-ciInstalls 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-debug-ci -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-debug-ci .github/skills/mz-debug-ci && 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-debug-ci" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-debug-ci into .github/skills/mz-debug-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-debug-ci", 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-debug-ci -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-debug-ci --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-debug-ci .opencode/skills/mz-debug-ci && 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-debug-ci" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-debug-ci into .opencode/skills/mz-debug-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-debug-ci", 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-debug-ci- GitHub stars
- 6.4k
- Token cost
- ~3.9k tokens
- SKILL.md length
- 2,093 words
- Files
- 3
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigate CI failures on PR via gh + Buildkite MCP or bk CLI.
- Works in 5 steps: Find the build → Check annotations first → Fetch logs when needed → …
- Tasks that involve Failing and flaky tests
- SKILL.md covers Prerequisites, Buildkite MCP: preferred when…, Search existing failures by… and Step 1: Find the build, plus 4 more sections
- Calls gh, git and jq; reaches buildkite.com and mcp.buildkite.com
What it does
Mz Debug CI is an agent skill from MaterializeInc/materialize. Investigate CI failures on PR via gh + Buildkite MCP or bk CLI. Trigger: failing checks, Buildkite failures, CI issues — "why is CI red", "build broken", "checks failing", "what went wrong in CI", "nightly broke", "tests failing on this PR", or pasted Buildkite URL. Also PR number + why failing.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `bk-fallback.md` and `rare-failures.md`).
It sits in Testing & QA, covering Failing and flaky tests. It works with Model Context Protocol 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 Failing and flaky tests
Example prompts
- “why is CI red”
- “build broken”
- “checks failing”
- “/mz-debug-ci”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Find the build
- Check annotations first
- Fetch logs when needed
- Categorize failures
- Summarize
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
Shell commands in SKILL.md call:
ghgitjqclaude
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
buildkite.commcp.buildkite.comlinear.app
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 Debug CI loads about 3.9k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 2,093 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 2,093 words (~3,923 tokens).
“Investigate CI failures for a Materialize PR or Buildkite build.”
- name
- mz-debug-ci
- argument-hint
- <PR number, GitHub PR URL, or Buildkite build URL>
Files
SKILL.md and 2 other files in .agents/skills/mz-debug-ci of MaterializeInc/materialize.
- SKILL.md
- bk-fallback.md
- rare-failures.md
Open the folder on GitHubat commit b760ecc
Compare with similar skills
Mz Debug CI 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 Debug CI this skillMaterializeInc/materialize | 6.4k | — | ~3.9k | Automated safety check: Pass | Custom licence | |
| Debugging Opik E2E Testscomet-ml/opik | 22k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Ue Test AuthoringJasonMa0012/MooaToon | 749 | — | ~2.1k | Automated safety check: Notes | Custom licence | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None | |
| Azsdk Common Pipeline AnalysisAzure/azure-sdk-tools | 134 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Playwright Healing AgentTahanima/playwright-java-test-automation-architecture | 113 | — | ~210 | Automated safety check: Pass | MIT |
Similar skills
Ue Test Authoring
JasonMa0012/MooaToon
A skill your agent uses when writing or modifying UE automated tests (Automation, CQTest, Functional, Gauntlet, LowLevel) with Rider MCP available.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
- Official
Azsdk Common Pipeline Analysis
Azure/azure-sdk-tools
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
Playwright Healing Agent
Tahanima/playwright-java-test-automation-architecture
Expert in diagnosing Playwright failures. Uses the @playwright MCP to verify live DOM state.
Opik Verify
comet-ml/opik-mcp
Decide ship or hold for a candidate from the compare skill's numbers, against an explicit release policy — regressions, pass rate, safety-tagged cases, subgroup consistency, latency and cost…
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 Limits Test
MaterializeInc/materialize
Add/modify/debug limits test. An agent skill from MaterializeInc/materialize.
Mz Parallel Workload
MaterializeInc/materialize
Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark).
Related
Works with
Categories
Questions about Mz Debug CI
What does Mz Debug CI do?
Investigate CI failures on PR via gh + Buildkite MCP or bk CLI. Mz Debug CI is an agent skill from MaterializeInc/materialize. Investigate CI failures on PR via gh + Buildkite MCP or bk CLI.
When should I use Mz Debug CI?
Mz Debug CI fits situations like: tasks that involve Failing and flaky tests.
How do I install Mz Debug CI in Claude Code?
Run `npx skills add MaterializeInc/materialize --skill mz-debug-ci -a claude-code`. Or copy the skill folder (.agents/skills/mz-debug-ci in MaterializeInc/materialize) into .claude/skills/mz-debug-ci in your project. Claude Code loads it when a task matches its description.
How do I install Mz Debug CI in Codex?
Run `npx skills add MaterializeInc/materialize --skill mz-debug-ci -a codex`. Or copy the skill folder (.agents/skills/mz-debug-ci in MaterializeInc/materialize) into .agents/skills/mz-debug-ci in your project. Codex loads it when a task matches its description.
Can I use Mz Debug CI 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-debug-ci -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-debug-ci, .gemini/skills/mz-debug-ci, .github/skills/mz-debug-ci and .opencode/skills/mz-debug-ci in your project.
What does Mz Debug CI need to run?
Going by SKILL.md and its folder, Mz Debug CI needs the command-line tools its instructions call (gh, git, jq and claude).
Does Mz Debug CI access the network?
SKILL.md names 3 domains. In commands or code: buildkite.com, mcp.buildkite.com and linear.app; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Mz Debug CI 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 Debug CI use?
Mz Debug CI 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 Debug CI use?
About 3.9k tokens (SKILL.md is roughly 16k 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 Debug CI?
Skills that share tags, products or a category with Mz Debug CI: Debugging Opik E2E Tests (comet-ml/opik, 22k stars), Ue Test Authoring (JasonMa0012/MooaToon, 749 stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars) and Azsdk Common Pipeline Analysis (Azure/azure-sdk-tools, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mz Debug CI?
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.