Dashboard Preview
m4r1k/Eneru
Visually verify Eneru browser-dashboard changes against a live daemon or audit an exact deployment.
Verify a release candidate on the Grafana dashboards and sign off in release.
Install Mz Release Signoff
$ npx skills add MaterializeInc/materialize --skill mz-release-signoff -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-release-signoff --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-release-signoff .claude/skills/mz-release-signoff && 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-release-signoff" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-release-signoff into .claude/skills/mz-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-release-signoff", 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-release-signoffType 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-release-signoff -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-release-signoff --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-release-signoff .agents/skills/mz-release-signoff && 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-release-signoff" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-release-signoff into .agents/skills/mz-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-release-signoff", 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-release-signoff -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-release-signoff --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-release-signoff .cursor/skills/mz-release-signoff && 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-release-signoff" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-release-signoff into .cursor/skills/mz-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-release-signoff", 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-release-signoff--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-release-signoff -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-release-signoff --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-release-signoff .gemini/skills/mz-release-signoff && 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-release-signoff" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-release-signoff into .gemini/skills/mz-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-release-signoff", 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-release-signoffInstalls 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-release-signoff -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-release-signoff .github/skills/mz-release-signoff && 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-release-signoff" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-release-signoff into .github/skills/mz-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-release-signoff", 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-release-signoff -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-release-signoff --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-release-signoff .opencode/skills/mz-release-signoff && 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-release-signoff" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-release-signoff into .opencode/skills/mz-release-signoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-release-signoff", 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-release-signoff- GitHub stars
- 6.4k
- Token cost
- ~7.2k tokens
- SKILL.md length
- 3,984 words
- Files
- 13 (incl. scripts, references)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Verify a release candidate on the Grafana dashboards and sign off in release.
- Works in 8 steps: Establish the version and the boundaries → Choose the namespace set → Choose the time window → …
- Tasks that involve Monitoring and alerting
- SKILL.md covers Prerequisites, Read the panel instructions,…, Every dashboard names its… and Step 1: Establish the version…, plus 11 more sections
- Runs Python and Shell scripts from its folder; calls git
What it does
Mz Release Signoff is an agent skill from MaterializeInc/materialize. Verify a release candidate on the Grafana dashboards and sign off in release. Trigger: "verify the release", "sign off on the release", "release verification", "check the canary", "does this release look healthy", a pasted grafana.dev.materialize.com dashboard link, or a release-bot "please verify the vX.Y.Z" request. Also when asked to compare metrics across a release boundary.
Its SKILL.md is about 7.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including scripts and reference files (for example `references/adapter.md`, `references/compute.md` and `references/persist.md`).
It sits in DevOps & Cloud, covering Monitoring and alerting and Deployment. It works with Grafana 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 Monitoring and alerting
- Tasks that involve Deployment
Example prompts
- “verify the release”
- “sign off on the release”
- “release verification”
- “/mz-release-signoff”
Requirements
- Python 3
- A Bash shell
Workflow steps
8 steps, taken from the step headings in SKILL.md.
- Establish the version and the boundaries
- Choose the namespace set
- Choose the time window
- Derive the metric roster
- Measure
- Judge
- Drill deeper
- Report
What it can do on your machine
Read from SKILL.md and the folder at commit 6515d14. 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 7 files in scripts/ (Python and Shell), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 Release Signoff loads about 7.2k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 3,984 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); the scripts in this folder 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 3,984 words (~7,249 tokens).
“Verify a release candidate by comparing metrics across the release boundary, then report the outcome.”
- name
- mz-release-signoff
- argument-hint
- <release version, dashboard URL, or Slack thread URL>
Files
SKILL.md and 12 other files (scripts, references) in .agents/skills/mz-release-signoff of MaterializeInc/materialize.
- SKILL.md
- references/adapter.md
- references/compute.md
- references/persist.md
- references/reference-dashboards.md
- references/sources-and-sinks.md
- scripts/build-range-query.py
- scripts/catalog-diff.sh
- scripts/catalog_names.py
- scripts/lint_metrics.py
- scripts/lint_metrics_test.py
- scripts/metrics-allowlist.txt
- scripts/panel-metrics.py
Open the folder on GitHubat commit 6515d14
Compare with similar skills
Mz Release Signoff 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 Release Signoff this skillMaterializeInc/materialize | 6.4k | — | ~7.2k | Automated safety check: Pass | Custom licence | |
| Dashboard Previewm4r1k/Eneru | 149 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Aqua Metricsoracle/accelerated-data-science | 125 | — | ~1.5k | Automated safety check: Pass | UPL-1.0 | |
| App SDK Conceptsgrafana/skills | 281 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Analyzing Experiment Precompute CanaryPostHog/posthog | 40k | — | ~3.5k | Automated safety check: Pass | Custom licence | |
| Database Observabilitygrafana/skills | 281 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Aqua Metrics
oracle/accelerated-data-science
Set up Prometheus and Grafana monitoring for AQUA vLLM model deployments on OCI.
- Official
App SDK Concepts
grafana/skills
A skill your agent uses when starting any grafana-app-sdk work — scaffolding a Grafana app, initializing a Grafana App Platform app, picking a deployment mode (standalone operator / grafana/apps /…
- Official
Analyzing Experiment Precompute Canary
PostHog/posthog
Analyze the experiment precompute result-consistency canary across prod-US and prod-EU, deep-dive any issues, and produce an actionable report.
- Official
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…
Monitoring Agents Md
hardisgroupcom/sfdx-hardis
The AGENTS.md file that sf hardis:org:monitor:backup writes at the root of every monitoring repository, so a coding agent can answer questions about the org, its CI/CD deployments and its Grafana…
More from MaterializeInc/materialize
All 15 skills in this repoMz 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.
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 Release Signoff
What does Mz Release Signoff do?
Verify a release candidate on the Grafana dashboards and sign off in release. Mz Release Signoff is an agent skill from MaterializeInc/materialize. Verify a release candidate on the Grafana dashboards and sign off in release.
When should I use Mz Release Signoff?
Mz Release Signoff fits situations like: tasks that involve Monitoring and alerting; tasks that involve Deployment.
How do I install Mz Release Signoff in Claude Code?
Run `npx skills add MaterializeInc/materialize --skill mz-release-signoff -a claude-code`. Or copy the skill folder (.agents/skills/mz-release-signoff in MaterializeInc/materialize) into .claude/skills/mz-release-signoff in your project. Claude Code loads it when a task matches its description.
How do I install Mz Release Signoff in Codex?
Run `npx skills add MaterializeInc/materialize --skill mz-release-signoff -a codex`. Or copy the skill folder (.agents/skills/mz-release-signoff in MaterializeInc/materialize) into .agents/skills/mz-release-signoff in your project. Codex loads it when a task matches its description.
Can I use Mz Release Signoff 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-release-signoff -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-release-signoff, .gemini/skills/mz-release-signoff, .github/skills/mz-release-signoff and .opencode/skills/mz-release-signoff in your project.
What does Mz Release Signoff need to run?
Going by SKILL.md and its folder, Mz Release Signoff needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: Python 3; A Bash shell.
Does Mz Release Signoff access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Mz Release Signoff 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Mz Release Signoff use?
Mz Release Signoff 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 Release Signoff use?
About 7.2k tokens (SKILL.md is roughly 29k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.
What are the alternatives to Mz Release Signoff?
Skills that share tags, products or a category with Mz Release Signoff: Dashboard Preview (m4r1k/Eneru, 149 stars), Aqua Metrics (oracle/accelerated-data-science, 125 stars), App SDK Concepts (grafana/skills, 281 stars) and Analyzing Experiment Precompute Canary (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mz Release Signoff?
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 9, 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.