matlab-analyze-dependencies
Analyze the effective toolbox file set to produce a Dependency Manifest — classify all transitive dependencies as included, product, add-on, or external-unresolved, then present resolution options with tradeoffs. Use after matlab-define-toolbox-api when the spec is approved.
npx skills add matlab/matlab-agentic-toolkit --skill matlab-analyze-dependencies --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# matlab-analyze-dependencies — Dependency Analyzer You produce the **Dependency Manifest**: a complete picture of what the toolbox needs at runtime, what ships inside the .mltbx, and what doesn't. For anything that doesn't ship, you explain why and present resolution options. ## When to Use - After `matlab-define-toolbox-api` spec is approved, or user asks "what does this code depend on?" - Re-running after code changes to update the manifest ## When NOT to Use - Writing code or fixing bugs — this skill only analyzes, it does not modify source - Building the .mltbx — use `matlab-build-toolbox` after dependencies are resolved - Initial project setup — use `matlab-define-toolbox-api` first to define the toolbox spec ## Key Functions | Function | Purpose | |----------|---------| | `matlab.addons.toolbox.ToolboxOptions` | Determine effective file set (what ships) | | `matlab.codetools.requiredFilesAndProducts` | Trace transitive file and product dependencies | | `which` | Resolve namespace-qualified function names | | `exist` | Check if bare function names resolve | | `matlab.addons.installedAddons` | Correlate add-on file paths with metadata | ## Critical Pitfalls These three issues
- When to Use
- When NOT to Use
- Key Functions
- Critical Pitfalls
- Pitfall 1: Path Separator Mismatch (Windows)
- Pitfall 2: matlabroot File Leak
- Pitfall 3: Namespace Resolution Requires which()
- Core Concepts
- Workflow
- Phase 1 — Determine the Effective File Set
- Phase 2 — Trace Dependencies
- Phase 2b — Detect Unresolved Symbols
- Phase 3 — Transitive Closure of External Files
- Phase 4 — Present Results
What does the matlab-analyze-dependencies skill do?
Analyze the effective toolbox file set to produce a Dependency Manifest — classify all transitive dependencies as included, product, add-on, or external-unresolved, then present resolution options with tradeoffs. Use after matlab-define-toolbox-api when the spec is approved.
How do I install it?
Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-analyze-dependencies --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.