matlab/matlab-agentic-toolkit / skills-catalog/matlab-software-development/matlab-package-toolbox
matlab-package-toolbox
VerifiedTurn 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/unresolved-symbol-classification.md
View on GitHub# Unresolved Symbol Classification
## Classification Table
| Scenario | Detection | Resolution to suggest |
|----------|-----------|---------------------|
| **Typo** | Close edit-distance match to a known function | "Did you mean `fitlm`?" — suggest correction |
| **Exists on disk but not on path** | `dir('**/<name>.m')` finds it somewhere | Show where it lives — suggest adding to path or moving into toolbox |
| **From a product not installed** | Function name appears in MATLAB's product function database | "This requires [Toolbox Name] which is not installed" |
| **From an add-on not installed** | Function name matches known add-on content | Suggest installing the add-on and declaring it as a dependency |
| **Truly missing** | No match found anywhere | Flag for user — may be deleted code, a planned function, or a conditional dependency |
## Resolution Assistance
For each unresolved symbol:
1. **Fuzzy match**: Compute edit distance against all functions on the current path + known product functions. Suggest the top 1-3 closest matches.
2. **Disk search**: Search for `<symbolName>.m` in this order, stopping at the first hit:
1. The toolbox root itself (may be a namespace-resolution issue rather than a missing file)
2. Sibling directories of the toolbox root (e.g., `../shared-utils/`, `../helpers/`)
3. The git repository root and its subdirectories (if the toolbox is inside a git repo)
4. Directories currently on the MATLAB path (`path` output)
Do NOT search the entire filesystem — if the file is not found in these scopes, classify as "truly missing."
3. **Product lookup**: Check if the function belongs to a MathWorks product not currently installed (MATLAB maintains an internal function-to-product mapping; `matlab.codetools.requiredFilesAndProducts` uses this with `Certain == 0` for guesses, but fully missing products may not appear at all).
4. **Context clues**: If the unresolved symbol is called alongside known toolbox functions (e.g., in the same file as `fitlm`), suggest the same toolbox.
## Presentation Format
```
Unresolved Symbols:
├── fltlm (called from +pkg/analysis.m:42)
│ Likely typo — did you mean fitlm (Statistics and Machine Learning Toolbox)?
│
├── customPlot (called from +pkg/visualize.m:15, +pkg/report.m:88)
│ Found on disk: C:\Projects\SharedViz\customPlot.m (not on MATLAB path)
│ → This is also an external file dependency if added to path
│
└── generateReport (called from +pkg/main.m:102)
Not found anywhere — may be missing or not yet written.
```
## Connecting Symbols to File Decisions
If a symbol resolves to a file on disk, it becomes an external file dependency. Present it in both the unresolved symbols section (for diagnosis) and feed it into Phase 3 (for transitive closure if the user decides to include it).
----
Copyright 2026 The MathWorks, Inc.
----
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| 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: 197k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |