Create an experiment for the MATLAB Experiment Manager app from user code, script, or problem description. TRIGGER when: user asks to create an experiment from a script/function, wants to sweep parameters or hyperparameters, asks to compare configurations, or describes a problem suitable for experimentation. DO NOT TRIGGER when: user is debugging an existing experiment, wants to run/resume trials, or already has a working experiment set up.
SkillScore84Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 20 of 24 test cases with the skill, and 8 of 24 without it.
Without skill32%
With skill84%
Checks it passed that the model alone missed
Appends the suffix 'Project' to the project name.
Uses the section heading 'Generated Setup Function'.
Uses the section heading 'Generated Training Function'.
and 10 more in the full report
13 fixed8 passed either way4 still failing0 broke
Pass-rate lift
+52 pp
Tokens
+116%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/16/2026v121 of 25 cases passed with skill · 24 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
When generating the experiment object file for an experiment named Antenna, what naming suffix should be appended to the experiment name?
What was checked, without and with the skill
Checked
Without skill
With skill
Appends the suffix 'Experiment' to the experiment name.
Missed
Passed
case-20 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md252 lines3 filesincludes scripts
Create Experiment for Experiment Manager
Plans and creates experiments in MATLAB Experiment Manager by analyzing user code or problem
descriptions, determining the experiment type, and generating the appropriate experiment
function, hyperparameter table, and experiment object.
When to Use
User has a MATLAB script/function and wants to sweep parameters or hyperparameters
User asks to create an experiment or compare configurations
User describes a problem and wants to explore parameter space
User wants to track outputs across different parameter combinations
When NOT to Use
User is debugging an existing experiment or training failure
User wants to run, resume, or view results of an existing experiment
User already has a working Experiment Manager experiment set up
User wants to edit experiment settings (hyperparameters, strategy, description) — direct them to make changes in the Experiment Manager app. However, editing the experiment function code (.m file) is allowed.
User wants Bayesian optimization or random sampling strategy — direct them to configure from the Experiment Manager app
Autonomy Model
This skill follows a guidance + autonomy pattern. Decision points are tagged:
Tag
Meaning
[user]
Always pause and ask. Non-negotiable.
[auto]
Agent decides silently. Escalates on failure.
[depends]
Resolved by clarity of signals — auto if clear, ask if ambiguous.
After analysis, tell the user how you intend to work in one plain sentence.
Always add: "Let me know if you'd prefer more or less control."
Phase 1: Analysis
Read the user's code or problem description and classify the experiment type.