OPEN-SOURCE AGENT SKILL · v0.1.0

Let your agent propose.
Decide what reaches production.

Give Codex a repeatable MatrixOne workflow: branch the data, make changes, inspect the diff, validate every changed row, and promote only an approved proposal.

Download skill ZIP Install in your project

MIT license · Markdown + SQL guidance · No custom MCP required · No runtime telemetry

Instructions guide the agent. Permissions enforce the boundary.

The proposal agent should only be able to write its own branch. Keep production and merge credentials with a separate operator or service. Branches isolate data changes; heavy work still needs resource limits or a separate workspace instance.

START WITH YOUR EXISTING TOOLS

Install once. Bring your own MatrixOne.

Download and inspect
Unzip the package and read its instructions. It contains no executable installer, database password, or automatic connection.
ZIP · 11.1 KB · SHA-256 b1749da28093c1b18ff7dd9e690607f80ba000aab8fa26ccee4d42fca8b19696
SHA256SUMS
Add it to your project
For Codex, place the extracted folder here, then open the project. If the skill does not appear, restart Codex. For other agents, use their supported skill directory.
```
your-project/
└── .agents/skills/
    └── matrixone-safe-data-changes/
        ├── SKILL.md
        ├── agents/openai.yaml
        └── references/
```
Official Codex skill installation guide →

Ask for a reviewed proposal

Use your existing MySQL client or database tool with branch-scoped credentials. Start on a small disposable dataset to check the installed MatrixOne version.

Codex prompt

Use $matrixone-safe-data-changes to normalize brands
in my product catalog. Change only brand;
protect price, SKU, and every other field.
Prepare the branch and review report.
Do not merge until I approve the exact proposal.

SKILL + YOUR CLIENT TODAY

When do you need another tool?

Operator-led workflow

Use this skill with a MySQL client. An operator provisions restricted branch access and promotes reviewed changes in a separate session. No dedicated MCP server is required.

Available in this download

Unattended or multi-user workflow

Add a local CLI or service that owns credentials and enforces workspace scope, immutable proposals, approvals, resource limits, and merge recovery. MCP is one optional interface. That service is not included in this release.

Build when your workflow needs it

OPEN DISTRIBUTION

Downloads you can inspect.

This counter comes from the GitHub release asset for v0.1.0. Repeat downloads, bots and verification requests can count. It does not measure unique people, installs, successful runs or active users.

The installed skill sends no telemetry. GitHub serves the download; This page reads only its public aggregate count, requesting it directly from GitHub without cookies if the website cache is unavailable. Counts may be delayed or temporarily unavailable.

View the release →

—downloads of this versionLoading GitHub count…

Tried it on your own data?

Share an optional, public experience report: your workload, MatrixOne version, whether branch → review → merge worked, and what got in the way. Include no credentials, private data or customer details.

Share your experience See the 10M-row experiment

The published experiment used synthetic data and 20 Codex-authored SQL plans. It demonstrated the database workflow, not a complete production permission boundary.