New Lint
supabase/splinter
Create a new splinter lint — a SQL view that checks for a database anti-pattern.
Trigger: "run Materialize locally", "start environmentd", "check compilation", "format code", "lint", "cargo check", "cargo fmt", "cargo clippy", "bin/fmt", "bin/lint", or mentions compiling…
Install Mz Run
$ npx skills add MaterializeInc/materialize --skill mz-run -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-run --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-run .claude/skills/mz-run && 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-run" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-run into .claude/skills/mz-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-run", 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-runType 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-run -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-run --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-run .agents/skills/mz-run && 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-run" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-run into .agents/skills/mz-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-run", 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-run -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-run --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-run .cursor/skills/mz-run && 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-run" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-run into .cursor/skills/mz-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-run", 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-run--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-run -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-run --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-run .gemini/skills/mz-run && 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-run" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-run into .gemini/skills/mz-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-run", 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-runInstalls 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-run -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-run .github/skills/mz-run && 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-run" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-run into .github/skills/mz-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-run", 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-run -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-run --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-run .opencode/skills/mz-run && 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-run" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-run into .opencode/skills/mz-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-run", 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-run- GitHub stars
- 6.4k
- Token cost
- ~970 tokens
- SKILL.md length
- 439 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Trigger: "run Materialize locally", "start environmentd", "check compilation", "format code", "lint", "cargo check", "cargo fmt", "cargo clippy", "bin/fmt", "bin/lint", or mentions compiling…
- Tasks that involve Linting and formatting
- SKILL.md covers Compiling, Running locally, Formatting and linting and Log filters, plus 1 more section
- Calls cargo, docker and psql
What it does
Mz Run is an agent skill from MaterializeInc/materialize. Trigger: "run Materialize locally", "start environmentd", "check compilation", "format code", "lint", "cargo check", "cargo fmt", "cargo clippy", "bin/fmt", "bin/lint", or mentions compiling, building, running, formatting, linting, log filters, jemalloc, CockroachDB setup in Materialize. Also "how do I run this" or "it won't compile".
Its SKILL.md is about 970 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 Development, covering Linting and formatting. 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 Linting and formatting
Example prompts
- “run Materialize locally”
- “start environmentd”
- “check compilation”
- “/mz-run”
Requirements
- Docker
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:
cargodockerpsql
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, 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 Run loads about 970 tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 439 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 439 words (~970 tokens).
“Check compilation with cargo check. Do not use cargo build or cargo run to build or run Materialize. Use bin/environmentd --build-only to build without running.”
- name
- mz-run
Files
Just SKILL.md in .agents/skills/mz-run of MaterializeInc/materialize.
Open the folder on GitHubat commit b760ecc
Compare with similar skills
Mz Run 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 Run this skillMaterializeInc/materialize | 6.4k | — | ~970 | Automated safety check: Pass | Custom licence | |
| New Lintsupabase/splinter | 280 | — | ~2.9k | Automated safety check: Notes | None | |
| Rsigmatimescale/rsigma | 159 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Repo Guardsimovilab/databus | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Diesel Guardayarotsky/diesel-guard | 121 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Gateguardana/guardana | 129 | — | ~776 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Rsigma
timescale/rsigma
Use the rsigma CLI and MCP server: engine eval, engine daemon, rule lint, rule draft, rule tune, rule backtest, backend convert, mcp serve.
Repo Guard
simovilab/databus
Keep the databus repo clean as it grows — verify new/changed backend code meets the project's docstring, type-hint, and structural conventions, and update any docs the change made stale.
Diesel Guard
ayarotsky/diesel-guard
Lints Diesel and SQLx Postgres migrations for unsafe schema changes that lock tables or cause downtime, and authors custom Rhai checks.
Gate
guardana/guardana
Run this project's verification — the full local CI mirror (ruff, mypy, import contract, pytest with PostgreSQL, coverage floors, dogfood, generated docs and site, the isolated example suites, the…
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
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 Run
What does Mz Run do?
Trigger: "run Materialize locally", "start environmentd", "check compilation", "format code", "lint", "cargo check", "cargo fmt", "cargo clippy", "bin/fmt", "bin/lint", or mentions compiling…. Mz Run is an agent skill from MaterializeInc/materialize. Trigger: "run Materialize locally", "start environmentd", "check compilation", "format code", "lint", "cargo check", "cargo fmt", "cargo clippy", "bin/fmt", "bin/lint", or mentions compiling, building, running, formatting, linting, log filters, jemalloc, CockroachDB setup in Materialize.
When should I use Mz Run?
Mz Run fits situations like: tasks that involve Linting and formatting.
How do I install Mz Run in Claude Code?
Run `npx skills add MaterializeInc/materialize --skill mz-run -a claude-code`. Or copy the skill folder (.agents/skills/mz-run in MaterializeInc/materialize) into .claude/skills/mz-run in your project. Claude Code loads it when a task matches its description.
How do I install Mz Run in Codex?
Run `npx skills add MaterializeInc/materialize --skill mz-run -a codex`. Or copy the skill folder (.agents/skills/mz-run in MaterializeInc/materialize) into .agents/skills/mz-run in your project. Codex loads it when a task matches its description.
Can I use Mz Run 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-run -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-run, .gemini/skills/mz-run, .github/skills/mz-run and .opencode/skills/mz-run in your project.
What does Mz Run need to run?
Going by SKILL.md and its folder, Mz Run needs the command-line tools its instructions call (cargo, docker and psql). Our summary lists: Docker.
Does Mz Run access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Mz Run 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 Run use?
Mz Run 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 Run use?
About 970 tokens (SKILL.md is roughly 3.9k 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 Run?
Skills that share tags, products or a category with Mz Run: New Lint (supabase/splinter, 280 stars), Rsigma (timescale/rsigma, 159 stars), Repo Guard (simovilab/databus, 101 stars) and Diesel Guard (ayarotsky/diesel-guard, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mz Run?
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.