Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
Run tests + pick test framework in Materialize. An agent skill from MaterializeInc/materialize.
Install Mz Test
$ npx skills add MaterializeInc/materialize --skill mz-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-test --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-test .claude/skills/mz-test && 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-test" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-test into .claude/skills/mz-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-test", 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-testType 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-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-test --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-test .agents/skills/mz-test && 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-test" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-test into .agents/skills/mz-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-test", 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-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-test --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-test .cursor/skills/mz-test && 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-test" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-test into .cursor/skills/mz-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-test", 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-test--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-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-test --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-test .gemini/skills/mz-test && 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-test" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-test into .gemini/skills/mz-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-test", 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-testInstalls 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-test -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-test .github/skills/mz-test && 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-test" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-test into .github/skills/mz-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-test", 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-test -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-test --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-test .opencode/skills/mz-test && 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-test" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-test into .opencode/skills/mz-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-test", 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-test- GitHub stars
- 6.4k
- Token cost
- ~3.2k tokens
- SKILL.md length
- 1,512 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Run tests + pick test framework in Materialize. An agent skill from MaterializeInc/materialize.
- Works in 2 steps: With the fix removed run the test and… → Restore the fix, run the test again, and…
- Tasks that involve Failing and flaky tests
- SKILL.md covers Cluster sizes, Unit tests, sqllogictest and When sqllogictest gives…, plus 7 more sections
- Calls cargo
What it does
Mz Test is an agent skill from MaterializeInc/materialize. Run tests + pick test framework in Materialize. Trigger: "run tests", "run testdrive", "run sqllogictest", "run mzcompose", "run cargo test", "run pgtest", "rewrite test results", "add a test", "reproduce a bug", "write a regression test", or mentions testing, testdrive, sqllogictest, mzcompose, pgtest, cargo test, nextest, flaky tests, test failures. Also "test this" or "how do I verify this works". Specifics: mz-platform-checks (upgrade/restart survival), mz-parallel-workload (concurrent stress), mz-limits-test…
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Failing and flaky tests. It works with 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
- “run tests”
- “run testdrive”
- “run sqllogictest”
- “/mz-test”
Requirements
- Python 3
- Docker
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- With the fix removed run the test and confirm it fails, for the expected reason. Read the failure output.
- Restore the fix, run the test again, and confirm it passes.
What it can do on your machine
Read from SKILL.md and the folder at commit 80f0437. 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:
cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
ci.dev.materialize.com
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 Test loads about 3.2k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 1,512 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 1,512 words (~3,217 tokens).
“mzcompose-based tests and bin/environmentd take their cluster replica sizes from cluster_replica_size_map() in misc/python/materialize/mzcompose/init.py, named scale=,workers=[,mem=GiB], e.g. CREATE CLUSTER c SIZE 'scale=1,workers=1'. Plain sizes like '1' fail there with "unknown cluster replica size". The emulator image run directly knows only cloud-style…”
- name
- mz-test
Files
Just SKILL.md in .agents/skills/mz-test of MaterializeInc/materialize.
Open the folder on GitHubat commit 80f0437
Compare with similar skills
Mz Test 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 Test this skillMaterializeInc/materialize | 6.4k | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Pester Failure AnalysisPowerShell/PowerShell | 56k | — | ~5.1k | Automated safety check: Pass | MIT | |
| Cucumber and Playwright E2E Testslanggenius/dify | 158k | — | ~682 | Automated safety check: Pass | Custom licence | |
| Diagnose Playwright Failure as Product Bugappsmithorg/appsmith | 41k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Apple Container Test RunnerRustPython/RustPython | 22k | — | ~467 | Automated safety check: Pass | MIT | |
| Fix Failing Playwright Specappsmithorg/appsmith | 41k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
Apple Container Test Runner
RustPython/RustPython
Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.
Fix Failing Playwright Spec
appsmithorg/appsmith
Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions.
Update V86
felixrieseberg/windows95
Build and install v86 (wasm + libv86.js + BIOS) into windows95.
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 Test
What does Mz Test do?
Run tests + pick test framework in Materialize. An agent skill from MaterializeInc/materialize. Mz Test is an agent skill from MaterializeInc/materialize. Run tests + pick test framework in Materialize.
When should I use Mz Test?
Mz Test fits situations like: tasks that involve Failing and flaky tests.
How do I install Mz Test in Claude Code?
Run `npx skills add MaterializeInc/materialize --skill mz-test -a claude-code`. Or copy the skill folder (.agents/skills/mz-test in MaterializeInc/materialize) into .claude/skills/mz-test in your project. Claude Code loads it when a task matches its description.
How do I install Mz Test in Codex?
Run `npx skills add MaterializeInc/materialize --skill mz-test -a codex`. Or copy the skill folder (.agents/skills/mz-test in MaterializeInc/materialize) into .agents/skills/mz-test in your project. Codex loads it when a task matches its description.
Can I use Mz Test 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-test -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-test, .gemini/skills/mz-test, .github/skills/mz-test and .opencode/skills/mz-test in your project.
What does Mz Test need to run?
Going by SKILL.md and its folder, Mz Test needs the command-line tools its instructions call (cargo). Our summary lists: Python 3; Docker.
Does Mz Test access the network?
SKILL.md names 1 domain. As links in the text: ci.dev.materialize.com. This is read from the text; nothing was executed.
Is Mz Test 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 Test use?
Mz Test 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 Test use?
About 3.2k tokens (SKILL.md is roughly 13k 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 Test?
Skills that share tags, products or a category with Mz Test: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars), Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars) and Apple Container Test Runner (RustPython/RustPython, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mz Test?
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 7, 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.