Agent skill · Backend & API

matlab-define-toolbox-api

Scan a folder, triage files into include/exclude, identify the public API, and produce a toolboxSpecification.m Interface Spec — all in one pass. Use when turning loose code into a toolbox.

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

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

Facts
Files in the skill folder: 3
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0
Declared author: MathWorks
Path: skills-catalog/matlab-software-development/matlab-define-toolbox-api/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-define-toolbox-api — Toolbox Scope & Spec Generator You take a folder of code, figure out what belongs in the toolbox, identify the public API, and produce the Interface Spec — the contract defining what the toolbox exposes. One skill, one artifact. ## When to Use - User wants to turn code into a toolbox - User points at a folder and says "make this a toolbox" or "package this" - User has a mix of scripts, functions, tests, data, and scratch files - Starting the files-to-package pipeline from scratch ## When NOT to Use - Adding files to an existing spec — edit `buildUtilities/toolboxSpecification.m` directly - Analyzing dependencies — use `matlab-analyze-dependencies` after the spec is approved - Building the .mltbx package — use `matlab-build-toolbox` - Documenting the toolbox — use `matlab-document-toolbox` ## Key Functions | Function | Purpose | |----------|---------| | `dir` | Recursive file listing for inventory | | `which` | Resolve function locations on path | | `exist` | Check whether a name resolves to a file, folder, or built-in | | `matlab.codetools.requiredFilesAndProducts` | Trace caller/callee relationships for Support classification | ## Inputs | Input | Req

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 1 — Gather Inputs
  7. Step 2 — Inventory the Folder
  8. Step 3 — Classify Relevance
  9. Step 4 — Identify Public API
  10. Step 5 — Present Report & Get Confirmation
  11. Step 6 — Generate Interface Spec
  12. Output
  13. Checkpoint
  14. Key Rules
Ships with 2 files
  • manifest.yaml
  • scripts/toolboxSpecificationTemplate.m
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-define-toolbox-api skill do?

Scan a folder, triage files into include/exclude, identify the public API, and produce a toolboxSpecification.m Interface Spec — all in one pass. Use when turning loose code into a toolbox.

How do I install it?

Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-define-toolbox-api --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