SQL Database Support for pREST
prest/prest
Guides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects.
Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark).
Install Mz Parallel Workload
$ npx skills add MaterializeInc/materialize --skill mz-parallel-workload -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MaterializeInc/materialize mz-parallel-workload --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-parallel-workload .claude/skills/mz-parallel-workload && 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-parallel-workload" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-parallel-workload into .claude/skills/mz-parallel-workload/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-parallel-workload", 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-parallel-workloadType 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-parallel-workload -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MaterializeInc/materialize mz-parallel-workload --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-parallel-workload .agents/skills/mz-parallel-workload && 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-parallel-workload" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-parallel-workload into .agents/skills/mz-parallel-workload/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-parallel-workload", 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-parallel-workload -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MaterializeInc/materialize mz-parallel-workload --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-parallel-workload .cursor/skills/mz-parallel-workload && 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-parallel-workload" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-parallel-workload into .cursor/skills/mz-parallel-workload/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-parallel-workload", 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-parallel-workload--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-parallel-workload -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MaterializeInc/materialize mz-parallel-workload --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-parallel-workload .gemini/skills/mz-parallel-workload && 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-parallel-workload" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-parallel-workload into .gemini/skills/mz-parallel-workload/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-parallel-workload", 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-parallel-workloadInstalls 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-parallel-workload -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-parallel-workload .github/skills/mz-parallel-workload && 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-parallel-workload" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-parallel-workload into .github/skills/mz-parallel-workload/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-parallel-workload", 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-parallel-workload -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-parallel-workload --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-parallel-workload .opencode/skills/mz-parallel-workload && 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-parallel-workload" agent skill from https://github.com/MaterializeInc/materialize/tree/main/.agents/skills/mz-parallel-workload into .opencode/skills/mz-parallel-workload/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mz-parallel-workload", 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-parallel-workload- GitHub stars
- 6.4k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 514 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark).
- Works in 3 steps: Define the Action Class → Override errors_to_ignore() If Needed → Register in an Action List
- Tasks that involve SQL
- SKILL.md covers When to Use This Framework, How It Works, Adding a New Action and Common Patterns, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mz Parallel Workload is an agent skill from MaterializeInc/materialize. Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark). Trigger: "parallel workload", "parallel-workload", "action.py" re parallel workload, or testing panics/unexpected errors under concurrency. Also "add this to parallel workload" or bug that panics under concurrent DDL/DML.
Its SKILL.md is about 1.9k 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 Databases, covering SQL. It works with SQL 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 SQL
Example prompts
- “parallel workload”
- “parallel-workload”
- “action.py”
- “/mz-parallel-workload”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Define the Action Class
- Override errors_to_ignore() If Needed
- Register in an Action List
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
No scripts in the folder and no shell commands in SKILL.md (its code samples are python and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Parallel Workload loads about 1.9k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 514 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 514 words (~1,892 tokens).
“The parallel-workload framework stress-tests Materialize by running random SQL actions concurrently across multiple threads. It catches panics and unexpected query errors - it does not verify result correctness.”
- name
- mz-parallel-workload
Files
Just SKILL.md in .agents/skills/mz-parallel-workload of MaterializeInc/materialize.
Open the folder on GitHubat commit 80f0437
Compare with similar skills
Mz Parallel Workload 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 Parallel Workload this skillMaterializeInc/materialize | 6.4k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| SQL Database Support for pRESTprest/prest | 4.6k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Chdb SQLvemetric/vemetric | 394 | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Schema Explorationtimescale/pg-aiguide | 1.9k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Dingtalk AitableDingTalk-Real-AI/dingtalk-workspace-cli | 3.2k | — | ~5.4k | Automated safety check: Pass | Apache-2.0 | |
| Sql2erystemsrx/sql_to_ER | 188 | — | ~1.1k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Chdb SQL
vemetric/vemetric
A skill your agent uses when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse…
Schema Exploration
timescale/pg-aiguide
Explore an existing PostgreSQL database before answering questions about its data or writing SQL.
Dingtalk Aitable
DingTalk-Real-AI/dingtalk-workspace-cli
钉钉 AI 表格（多维表）业务操作。Use when 用户需要操作 AI 表格/多维表/Base/Table、应用模式/App 页面/Widget、建表、查写记录、字段、记录评论、评论回复、访问密钥（API Key）、SQL/PostgreSQL/SELECT/JOIN、筛选、排序、公式、模板、批量导入 CSV 或 JSON、导出、仪表盘、图表、上传附件、数据源配置与同步、按任务 ID…
Sql2er
ystemsrx/sql_to_ER
A skill your agent uses when the user wants a Chen-model ER diagram from SQL CREATE TABLE statements or DBML, wants to rearrange or clean up an existing sql2er state, wants a skeleton-only overview…
PostgreSQL Documentation Reference
2025Emma/vibe-coding-cn
PostgreSQL database documentation - SQL queries, database design, administration, performance tuning, and advanced features. Use when working with PostgreSQL…
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 Parallel Workload
What does Mz Parallel Workload do?
Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark). Mz Parallel Workload is an agent skill from MaterializeInc/materialize. Extend parallel-workload stress framework: random SQL concurrently to catch panics + unexpected errors (not perf — see mz-benchmark).
When should I use Mz Parallel Workload?
Mz Parallel Workload fits situations like: tasks that involve SQL.
How do I install Mz Parallel Workload in Claude Code?
Run `npx skills add MaterializeInc/materialize --skill mz-parallel-workload -a claude-code`. Or copy the skill folder (.agents/skills/mz-parallel-workload in MaterializeInc/materialize) into .claude/skills/mz-parallel-workload in your project. Claude Code loads it when a task matches its description.
How do I install Mz Parallel Workload in Codex?
Run `npx skills add MaterializeInc/materialize --skill mz-parallel-workload -a codex`. Or copy the skill folder (.agents/skills/mz-parallel-workload in MaterializeInc/materialize) into .agents/skills/mz-parallel-workload in your project. Codex loads it when a task matches its description.
Can I use Mz Parallel Workload 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-parallel-workload -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-parallel-workload, .gemini/skills/mz-parallel-workload, .github/skills/mz-parallel-workload and .opencode/skills/mz-parallel-workload in your project.
What does Mz Parallel Workload need to run?
SKILL.md names no scripts, command-line tools or credentials: Mz Parallel Workload is instructions for the agent only. Our summary lists: Python 3.
Does Mz Parallel Workload access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mz Parallel Workload 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 Parallel Workload use?
Mz Parallel Workload 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 Parallel Workload use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 Parallel Workload?
Skills that share tags, products or a category with Mz Parallel Workload: SQL Database Support for pREST (prest/prest, 4.6k stars), Chdb SQL (vemetric/vemetric, 394 stars), Schema Exploration (timescale/pg-aiguide, 1.9k stars) and Dingtalk Aitable (DingTalk-Real-AI/dingtalk-workspace-cli, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mz Parallel Workload?
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.