Translate NI-DAQmx C function signatures into correct calldaqlib MATLAB calls.
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 21 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill95%
Checks it passed that the model alone missed
Uses uifigure to create the application window.
Uses uiaxes to create the plotting axes component.
States that calldaqlib property values must be scalar.
and 16 more in the full report
11 fixed10 passed either way1 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+62%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/16/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
I need to check if NI hardware device 'Dev1' is simulated using DAQmxGetDevIsSimulated in MATLAB R2026a+. Should I add channels to my daq object before calling calldaqlib, and what structure does the return value take?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses an empty daq object created without adding channels.
Missed
Passed
States that device-level queries return a plain scalar rather than a dictionary.
Missed
Passed
case-10 · 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.md242 lines4 files
matlab-call-nidaqmx
Translate NI-DAQmx C signatures into correct calldaqlib MATLAB calls on
Data Acquisition Toolbox R2026a+.
When to Use
User explicitly mentions calldaqlib or a specific DAQmx* C function
User needs NI-DAQmx capability the daq object doesn't expose (retriggerable,
export signal, reference triggers, enhanced alias rejection, digital filters)
User is debugging at the driver level (reading back what the NI driver holds)
User is translating existing C/LabVIEW code to MATLAB
When NOT to Use
User describes a capability achievable with the daq object alone (dq.Rate,
addtrigger, addclock, addinput, read, write, start, stop)
User asks about the Session-based (legacy) DAQ interface
User needs DAQmxCreateTask or DAQmxLoadTask (these cannot work through
calldaqlib — it owns task creation internally)
Decision Tree
Step 0 — Read the user's intent
Did the user explicitly mention calldaqlib or a specific DAQmx C function?
Yes — Write the calldaqlib call they asked for. Do NOT redirect to the
daq object. They have a reason (driver debugging, matching C code, capability
gap, learning). Skip to Step 2.
No — They described a capability without naming calldaqlib. Go to Step 1.
Step 1 — Pick the right tool
Can the daq object property/method do this? (dq.Rate, addtrigger,
addclock, addinput, dq.NumScansAvailable, etc.)
Yes — Recommend the daq object. Mention calldaqlib only if the user needs
driver-level diagnostics or a capability outside daq object coverage.
Use this skill to classify tabular data end-to-end in MATLAB — load a dataset, prepare and clean it, select promising classifiers, train them, and compare accuracies with cross-validation, holdout, or hyperparameter optimization plus statistical tests. TRIGGER when: user asks to classify tabular data, pick classifiers for a dataset, compare classifier accuracy, run cross-validation or a holdout evaluation, or find the best model with statistical uncertainty. DO NOT TRIGGER when: user has non-tab