Skip to content

matlab/matlab-agentic-toolkit / skills-catalog/matlab-software-development/matlab-package-toolbox

matlab-package-toolbox

Verified

Turn raw MATLAB code into a published .mltbx toolbox — full pipeline from scope definition through packaging and release. Drives 8 phases with human checkpoints, enforcing ordering and dependencies. Use when asked to package, create a toolbox, or run the files-to-package pipeline.

references/phase-7-build.md

View on GitHub
# Phase 7: Build Toolbox

Execute the build pipeline. Mechanical execution — introspect the plan, run it, report results, stop on failure.

## Key Functions

| Function | Purpose |
|----------|---------|
| `matlab.buildtool.Plan.load` | Introspect the build plan |
| `buildtool` | Execute the pipeline |
| `dir` | Locate and verify `.mltbx` artifact |

## Step 7.1 — Verify Preconditions

1. Confirm `buildfile.m` exists
2. Check pipeline context (`toolboxSpecification.m` and `tbxManifest.m` present = full pipeline)
3. Confirm no blockers from Phase 6

## Step 7.2 — Introspect the Build Plan

```matlab
plan = matlab.buildtool.Plan.load("buildfile.m");
disp({plan.Tasks.Name})
```

Identify the **target task** (priority: user input → `package` task → terminal task producing `.mltbx`).

Report what will execute:
```
Build target: "package"
Dependency chain: check → test → package
```

## Step 7.3 — Execute

```matlab
buildtool <target>
```

| Task Type | On Failure |
|-----------|------------|
| CodeIssuesTask / "check" | Report findings, stop |
| TestTask / "test" | Report failures, stop |
| Coverage | Log warning (does not stop) |
| MexTask | Report error, stop |
| Packaging | Report error, stop |

## Step 7.4 — Verify Artifact

```matlab
mltbxFile = dir(fullfile("release", "*.mltbx"));
assert(~isempty(mltbxFile), "No .mltbx file found in release/");
assert(mltbxFile(1).bytes > 0, "Package file is empty");
fprintf("Package: %s (%.1f KB)\n", fullfile(mltbxFile(1).folder, mltbxFile(1).name), mltbxFile(1).bytes / 1024);
```

## Step 7.5 — Report Results

On success: report package path, size, per-stage results (analysis findings, test counts, coverage %, duration).

On failure — diagnose by category:
- **Test failure**: Show which tests failed and why. Offer to fix and retry.
- **Packaging failure**: Check for missing files, path issues, ignore-file conflicts.
- **Code analysis failure**: Show warnings and offer to fix.

Maximum 3 retries before stopping.

## Rules

- **Introspect first.** Never assume the task name or chain — discover it.
- **Stop on first failure.** Never continue past a failing stage.
- **Report everything.** Counts, percentages, durations.
- **Verify the artifact.** Check exists and non-zero size.
- **No decisions.** Execute the plan. Do not modify code, skip tests, or lower thresholds.

----

Copyright 2026 The MathWorks, Inc.

----
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall