Agent skill

matlab-debugging

Diagnose MATLAB errors and unexpected behavior. Breakpoints, workspace inspection, try-catch diagnostics, and common error patterns. Use when debugging functions, tracing errors, inspecting variables, or diagnosing runtime failures.

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

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

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Version: 2.0
Declared author: MathWorks
Path: skills-catalog/matlab-core/matlab-debugging/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

# Investigating and Debugging MATLAB Code with MCP Tools You have access to a live MATLAB session via MCP tools. Use them to actively investigate code — whether debugging errors, understanding behavior, or answering questions about how MATLAB code works. Don't just guess from code alone. ## When to Use - User encounters a MATLAB error message or unexpected result - User wants to set breakpoints or inspect variable state - Tracing why a function produces wrong output - NaN/Inf values appearing unexpectedly - A MATLAB MCP tool returns an error or exception — including runtime errors, syntax errors, undefined function/variable errors, or failed test results - User asks "why is my MATLAB code not working", "help me debug", or shares a MATLAB stack trace ## When NOT to Use - Code quality review without a runtime problem — use `matlab-reviewing-code` instead - Performance profiling — use performance optimization workflows - Writing tests for correctness — use `matlab-testing` instead - Understanding MATLAB APIs or language features without a specific bug ## Static Analysis vs Runtime Debugging Not every issue needs the live MATLAB session. Choose the right approach: - **Static analysis i

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Static Analysis vs Runtime Debugging
  4. Auto-Trigger on MATLAB Errors
  5. Available Tools
  6. Workflow
  7. 1. Understand the Goal
  8. 2. Gather Information via MATLAB
  9. 3. Investigate Iteratively
  10. 4. Question the Diagnosis
  11. Common Errors — What to Check First
  12. Gotchas
  13. Key Principles
Ships with 1 file
  • manifest.yaml
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-debugging skill do?

Diagnose MATLAB errors and unexpected behavior. Breakpoints, workspace inspection, try-catch diagnostics, and common error patterns. Use when debugging functions, tracing errors, inspecting variables, or diagnosing runtime failures.

How do I install it?

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