I see all the new skills in here https://github.com/matlab/matlab-agentic-toolkit/tree/main/skills-catalog/matlab-core
the thing is, the skills are not named in a manner that clarifies they are MATLAB skills. So a skill like "testing" or "debugging" can potentially be saved and be confusing if you test or debug non-matlab code.
I also asked claude about this and here was the response:
When it works fine vs. when it breaks down
It works fine if: the skill's internal description/trigger explicitly says "activate when working with MATLAB .m files" — the content governs behavior.
It breaks down if: the skill description is generic (e.g., "activate when the user asks to debug code"), in which case the LLM may load it for Python, JavaScript, etc. — causing confusion or wrong guidance.
The verdict on naming
Prefixing with matlab- (as the official matlab/skills repo does — matlab-test-creator, matlab-test-execution, matlab-performance-optimizer) is the right call and not just cosmetic. It serves two purposes: it disambiguates at the skill-selection stage, and it signals intent to the LLM when multiple skills are loaded simultaneously.
Concrete recommendation
If the skills in matlab-agentic-toolkit aren't already prefixed with matlab-, they should be renamed (e.g., matlab-debugging, matlab-testing). More importantly, the skill description and trigger condition inside each SKILL.md should explicitly scope it, something like: "Activate when the user is debugging MATLAB .m files or working in a MATLAB environment." The naming and the internal trigger language should reinforce each other — you can't rely on just one.
The official MathWorks matlab/skills repo already follows this convention, so aligning matlab-agentic-toolkit to the same matlab- prefix pattern would be consistent and safe.
Can we update these skill names for this purpose?
I see all the new skills in here https://github.com/matlab/matlab-agentic-toolkit/tree/main/skills-catalog/matlab-core
the thing is, the skills are not named in a manner that clarifies they are MATLAB skills. So a skill like "testing" or "debugging" can potentially be saved and be confusing if you test or debug non-matlab code.
I also asked claude about this and here was the response:
When it works fine vs. when it breaks down
It works fine if: the skill's internal description/trigger explicitly says "activate when working with MATLAB .m files" — the content governs behavior.
It breaks down if: the skill description is generic (e.g., "activate when the user asks to debug code"), in which case the LLM may load it for Python, JavaScript, etc. — causing confusion or wrong guidance.
The verdict on naming
Prefixing with matlab- (as the official matlab/skills repo does — matlab-test-creator, matlab-test-execution, matlab-performance-optimizer) is the right call and not just cosmetic. It serves two purposes: it disambiguates at the skill-selection stage, and it signals intent to the LLM when multiple skills are loaded simultaneously.
Concrete recommendation
If the skills in matlab-agentic-toolkit aren't already prefixed with matlab-, they should be renamed (e.g., matlab-debugging, matlab-testing). More importantly, the skill description and trigger condition inside each SKILL.md should explicitly scope it, something like: "Activate when the user is debugging MATLAB .m files or working in a MATLAB environment." The naming and the internal trigger language should reinforce each other — you can't rely on just one.
The official MathWorks matlab/skills repo already follows this convention, so aligning matlab-agentic-toolkit to the same matlab- prefix pattern would be consistent and safe.
Can we update these skill names for this purpose?