Agent skill · Documentation

matlab-document-toolbox

Generates all documentation artifacts for a MATLAB toolbox: README.md, functionSignatures.json, GettingStarted.m, and publishable examples with demos.xml help integration. Follows mathworks/toolboxdesign best practices. Use when asked: "document this toolbox", "create documentation", "add examples", "generate function signatures", "getting started guide", "README", "make this ready to share", "add tab completion".

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

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

Facts
Files in the skill folder: 7
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.0
Declared author: MathWorks
Path: skills-catalog/matlab-software-development/matlab-document-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-document-toolbox — Toolbox Documentation Generator You produce all documentation artifacts needed for a well-documented MATLAB toolbox: README, function signatures, getting started guide, and examples. You follow the [mathworks/toolboxdesign](https://github.com/mathworks/toolboxdesign) conventions throughout. ## When to Use - After `matlab-create-project` has set up the project structure - User says "document this toolbox" or "add documentation" - User says "create examples" or "generate function signatures" - User says "getting started guide" or "README" - Before `matlab-assess-toolbox` to satisfy documentation checks (1, 2, 10, 12, 15) - User says "make this ready to share" ## When NOT to Use - Writing or fixing MATLAB code — this skill generates documentation only - Building or packaging the toolbox — use `matlab-build-toolbox` - Assessing readiness — use `matlab-assess-toolbox` (which may delegate here) - Writing tests — tests are handled by test-generation skills, not documentation ## Inputs | Input | Required | Description | |-------|----------|-------------| | Project path | Yes | Absolute path to the toolbox project root | | Scope | No | Which artifacts to generate

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Inputs
  4. Rules
  5. Workflow
  6. Step 1 — Discover Project Structure
  7. Step 2 — Analyze Functions
  8. Step 3 — Present Plan
  9. Step 4 — Generate README.md
  10. Step 5 — Generate functionSignatures.json
  11. Step 6 — Generate GettingStarted.m
  12. Step 7 — Generate Examples
  13. Step 8 — Generate demos.xml
  14. Step 9 — Add to MATLAB Project
Ships with 6 files
  • manifest.yaml
  • references/demos-xml-template.xml
  • references/examples-conventions.md
  • references/function-signatures-rules.md
  • references/readme-template.md
  • scripts/getting-started-template.m
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-document-toolbox skill do?

Generates all documentation artifacts for a MATLAB toolbox: README.md, functionSignatures.json, GettingStarted.m, and publishable examples with demos.xml help integration. Follows mathworks/toolboxdesign best practices. Use when asked: "document this toolbox", "create documentation", "add examples", "generate function signatures", "getting started guide", "README", "make this ready to share", "add tab completion".

How do I install it?

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