matlab-call-nidaqmx
Translate NI-DAQmx C function signatures into correct calldaqlib MATLAB calls. Use when the user mentions calldaqlib, any DAQmx* C function name (DAQmxCfgSampClkTiming, DAQmxExportSignal, DAQmxSetStartTrigRetriggerable, DAQmxGetSampClkRate, etc.), or needs NI-DAQmx functionality not exposed by the daq object. Covers: projection rules (taskHandle implicit, output pointers become return values, buffer-size args, enum-as-string), multi-task semantics, start() clobber, device-level empty-daq workaround, dictionary returns, string getter placeholder, array getter placeholder. Trigger contexts: low-
npx skills add matlab/matlab-agentic-toolkit --skill matlab-call-nidaqmx --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-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 de
- When to Use
- When NOT to Use
- Decision Tree
- Step 0 — Read the user's intent
- Step 1 — Pick the right tool
- Step 2 — Device-level check
- Step 3 — Multi-task check
- Step 4 — Buffer placeholder check
- Step 5 — Enum check
- Call Forms
- 1. Config (DAQmxCfg)
- 2. Setter (DAQmxSet)
- 3. Getter — scalar (DAQmxGet returning numeric)
- 4. Getter — string (DAQmxGet with char output)
What does the matlab-call-nidaqmx skill do?
Translate NI-DAQmx C function signatures into correct calldaqlib MATLAB calls. Use when the user mentions calldaqlib, any DAQmx* C function name (DAQmxCfgSampClkTiming, DAQmxExportSignal, DAQmxSetStartTrigRetriggerable, DAQmxGetSampClkRate, etc.), or needs NI-DAQmx functionality not exposed by the daq object. Covers: projection rules (taskHandle implicit, output pointers become return values, buffer-size args, enum-as-string), multi-task semantics, start() clobber, device-level empty-daq workaround, dictionary returns, string getter placeholder, array getter placeholder. Trigger contexts: low-
How do I install it?
Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-call-nidaqmx --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.