Dbt Databricks PR Ready
databricks/dbt-databricks
A skill your agent uses for an open dbt-databricks pull request, including your own PR or a fork PR, to assess merge readiness and optionally repair selected gaps on the PR head branch.
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.
$ npx skills add MaterializeInc/materialize --skill mz-dbt-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-dbt-release --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-dbt-release .claude/skills/mz-dbt-release && 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-dbt-release" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-dbt-release into .claude/skills/mz-dbt-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-dbt-release", 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-dbt-releaseType 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-dbt-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-dbt-release --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-dbt-release .agents/skills/mz-dbt-release && 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-dbt-release" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-dbt-release into .agents/skills/mz-dbt-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-dbt-release", 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-dbt-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-dbt-release --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-dbt-release .cursor/skills/mz-dbt-release && 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-dbt-release" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-dbt-release into .cursor/skills/mz-dbt-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-dbt-release", 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-dbt-release--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-dbt-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-dbt-release --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-dbt-release .gemini/skills/mz-dbt-release && 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-dbt-release" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-dbt-release into .gemini/skills/mz-dbt-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-dbt-release", 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-dbt-releaseInstalls 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-dbt-release -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-dbt-release .github/skills/mz-dbt-release && 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-dbt-release" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-dbt-release into .github/skills/mz-dbt-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-dbt-release", 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-dbt-release -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-dbt-release --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-dbt-release .opencode/skills/mz-dbt-release && 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-dbt-release" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-dbt-release into .opencode/skills/mz-dbt-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-dbt-release", 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.
mz-dbt-releaseCut 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 Dbt Release is an agent skill from 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. Trigger: "cut a dbt release", "release dbt-materialize", "release the dbt adapter", "ship dbt-materialize vX.Y.Z", "publish dbt-materialize to PyPI", "bump dbt-materialize version", "new dbt adapter version". Use this skill even if the user just says "ship the dbt adapter" or pastes a feature PR and asks for "the next dbt release" without naming…
Its SKILL.md is about 1.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 Data & Analytics, covering Data pipelines and ETL and Changelog and release notes. It works with dbt 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.
Read from SKILL.md and the folder at commit b760ecc. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitghcargoFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mz Dbt Release loads about 1.2k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 419 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.
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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 419 words (~1,171 tokens).
“A release PR bumps the published version of the dbt-materialize PyPI package. It is mechanical: three files change, one commit, one PR.”
Just SKILL.md in .agents/skills/mz-dbt-release of MaterializeInc/materialize.
Open the folder on GitHubat commit b760ecc
Mz Dbt Release 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 Dbt Release this skillMaterializeInc/materialize | 6.4k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Dbt Databricks PR Readydatabricks/dbt-databricks | 380 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Erd Studio Setupliam-machine/erd-studio | 165 | — | ~8.5k | Automated safety check: Pass | Custom licence | |
| PR Verifydocglow/docglow | 148 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Migrating Dagster To Airflowastronomer/agents | 451 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Dbt Parser Refreshyu-iskw/dbt-artifacts-parser | 118 | — | ~716 | Automated safety check: Pass | Apache-2.0 |
databricks/dbt-databricks
A skill your agent uses for an open dbt-databricks pull request, including your own PR or a fork PR, to assess merge readiness and optionally repair selected gaps on the PR head branch.
liam-machine/erd-studio
Friendly, step-by-step setup for ERD Studio in an existing dbt project, for people who may be new to dbt or data modelling.
docglow/docglow
Verify a Docglow change actually works before submitting or merging a PR.
astronomer/agents
Guide for migrating Dagster projects to Apache Airflow 3 on Astro.
yu-iskw/dbt-artifacts-parser
Refreshes dbt artifact schemas from dbt-labs/dbt-core and regenerates Pydantic parser classes.
godatadriven/dbt-bouncer
Analyzes a dbt project and suggests dbt-bouncer checks that already pass (for existing projects) or a sensible starter config (for greenfield projects).
MaterializeInc/materialize
Verify a release candidate on the Grafana dashboards and sign off in release.
MaterializeInc/materialize
Add/modify/debug Materialize perf benchmark scenarios. An agent skill from MaterializeInc/materialize.
MaterializeInc/materialize
Trigger: "commit", "prepare commit", "create PR", "push", "open pull request", or mentions committing, pre-commit checks, pull requests in Materialize.
MaterializeInc/materialize
Investigate CI failures on PR via gh + Buildkite MCP or bk CLI.
MaterializeInc/materialize
Add/modify/debug limits test. An agent skill from MaterializeInc/materialize.
MaterializeInc/materialize
Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark).
Works with
Categories
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 Dbt Release is an agent skill from MaterializeInc/materialize.py, date the Unreleased CHANGELOG entry, and open the release PR with a Ship: <url body.
Mz Dbt Release fits situations like: tasks that involve Data pipelines and ETL; tasks that involve Changelog and release notes.
Run `npx skills add MaterializeInc/materialize --skill mz-dbt-release -a claude-code`. Or copy the skill folder (.agents/skills/mz-dbt-release in MaterializeInc/materialize) into .claude/skills/mz-dbt-release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add MaterializeInc/materialize --skill mz-dbt-release -a codex`. Or copy the skill folder (.agents/skills/mz-dbt-release in MaterializeInc/materialize) into .agents/skills/mz-dbt-release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MaterializeInc/materialize --skill mz-dbt-release -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-dbt-release, .gemini/skills/mz-dbt-release, .github/skills/mz-dbt-release and .opencode/skills/mz-dbt-release in your project.
Going by SKILL.md and its folder, Mz Dbt Release needs the command-line tools its instructions call (git, gh and cargo). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Mz Dbt Release has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Mz Dbt Release: Dbt Databricks PR Ready (databricks/dbt-databricks, 380 stars), Erd Studio Setup (liam-machine/erd-studio, 165 stars), PR Verify (docglow/docglow, 148 stars) and Migrating Dagster To Airflow (astronomer/agents, 451 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.