Agent skill

matlab-publish-toolbox

Version-stamp, re-package, and distribute the .mltbx toolbox. Sets version in ToolboxOptions, re-runs packageToolbox, and guides distribution. Requires explicit user confirmation.

matlabgithub.com/matlabGitHub ↗
claude-codecodexcopilotNOASSERTION
Install
npx skills add matlab/matlab-agentic-toolkit --skill matlab-publish-toolbox --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.0
Declared author: MathWorks
Path: skills-catalog/matlab-software-development/matlab-publish-toolbox/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 868
Language: MATLAB

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# matlab-publish-toolbox — Release Publisher You handle the final release step: version stamping, re-packaging with the release version baked in, and distribution. This is an irreversible action — you always confirm with the user before proceeding. ## When to Use - After `matlab-build-toolbox` produces a verified `.mltbx` - User says "publish this" or "release it" - As the final step in the full pipeline ## When NOT to Use - The toolbox has not been built yet — use `matlab-build-toolbox` first - User wants to iterate on packaging or fix issues — use `matlab-assess-toolbox` - User wants to update the spec or API — use `matlab-define-toolbox-api` - User wants to do a dry-run build without publishing — use `matlab-build-toolbox` ## Key Functions | Function | Purpose | |----------|---------| | `matlab.addons.toolbox.ToolboxOptions` | Load packaging configuration and set version | | `matlab.addons.toolbox.packageToolbox` | Package the toolbox with version baked in | | `matlab.addons.install` | Install a toolbox from `.mltbx` (for verification/distribution) | ## Inputs - **project_root**: Path to the project (default: current directory) - **version** (optional): Version to release (e.g.,

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Key Functions
  4. Inputs
  5. Workflow
  6. Step 0 — Confirm with User
  7. Step 1 — Validate Version
  8. Step 2 — Confirm Readiness
  9. Step 3 — Update Version Everywhere (BEFORE Packaging)
  10. Step 4 — Re-package with Release Version
  11. Step 5 — Distribute
  12. Step 6 — Report
  13. Output
  14. Checkpoint
Ships with 1 file
  • manifest.yaml
Commands it runs
Find all files containing the old version
grep -r "1.0.0" . --include="*.m" --include="*.md" --include="*.prj"
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-publish-toolbox skill do?

Version-stamp, re-package, and distribute the .mltbx toolbox. Sets version in ToolboxOptions, re-runs packageToolbox, and guides distribution. Requires explicit user confirmation.

How do I install it?

Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-publish-toolbox --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From matlab/matlab-agentic-toolkit, a repository with 868 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going