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/examples-conventions.md

View on GitHub
# Example Live Script Conventions

## Location

`toolbox/examples/` (ships to users inside the .mltbx)

## Format

Plain-text MATLAB scripts (`.m`) with `%%` section breaks per design guidelines:
> "Examples are an effective way for users to learn how to use your toolbox."

Generate one example per function or logical group.

## Naming Convention

`<descriptiveAction>.m` (e.g., `usingAdd.m`, `plotTimeSeries.m`)

## Structure Template

```matlab
%% Title: Descriptive Action with Function Name
% Brief description of what this example demonstrates.

%% Setup
% Load any required data or configure parameters.

data = [1 2 3 4 5];

%% Basic Usage
% Show the primary usage pattern.

result = functionName(data);
disp(result)

%% Visualization (if applicable)
% Show output graphically.

figure
plot(result)
title("Result of functionName")
xlabel("Index")
ylabel("Value")

%% Variations
% Show different parameter combinations or options.

result2 = functionName(data, Method="fast");
```

## Key Rules

- Each example MUST run without user interaction or modification
- Use `%%` section breaks for publishable format
- Include at least one usage demonstrating the primary function signature
- Add figures with titles, labels, and legends where appropriate
- Set `rng(seed)` before random number generation for reproducibility
- For GUI functions: demonstrate concepts programmatically, don't launch the GUI
- Keep execution time reasonable (< 30s per example; reduce problem size if needed)
- For functions requiring optional toolboxes: guard with `license('test', 'toolbox_name')`

## File Format

Write examples as plain-text `.m` files with `%%` section breaks. These render as rich documents in the MATLAB Live Editor and are version-control friendly. Do not convert to binary `.mlx`.

## Publishing to HTML (optional)

If the user wants HTML output for static hosting or offline viewing:

```matlab
addpath(toolboxFolder);
addpath(examplesPath);

htmlDir = fullfile(examplesPath, 'html');
mkdir(htmlDir);

opts = struct('format', 'html', 'outputDir', htmlDir, ...
    'showCode', true, 'evalCode', true, 'catchError', true);

exFiles = dir(fullfile(examplesPath, '*_example.m'));
for i = 1:length(exFiles)
    close all
    publish(fullfile(examplesPath, exFiles(i).name), opts);
end
```

Note: The examples folder MUST be on the MATLAB path before calling `publish` with `evalCode=true`.

----

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: 197kUpdated 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