Agent skill · Data & Analytics

matlab-fuse-inertial-sensors

Analyzes sensor configurations and creates inertial fusion filters in MATLAB Navigation Toolbox. Manages filter selection (imufilter, ahrsfilter, complementaryFilter, insfilterMARG, insfilterAsync, insfilterNonholonomic, insfilterErrorState, insEKF, insCF), construction, tuning, and fusion loops. Use when fusing IMU/AHRS/INS/GPS+IMU data, estimating orientation or pose, or choosing a filter. Do NOT use for vision-only SLAM, Simulink fusion, or IMU simulation.

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

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

Facts
Files in the skill folder: 6
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.1
Declared author: MathWorks
Requires: R2022a+
Path: skills-catalog/robotics-and-autonomous-systems/matlab-fuse-inertial-sensors/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

## When to Use Select, implement, or tune an inertial sensor fusion filter in MATLAB Navigation Toolbox. ## When NOT to Use - Vision-only or LiDAR-only SLAM (no inertial sensor): use nav SLAM functions instead - Sensor simulation or data generation only: no filter needed - Simulink model-based sensor fusion --- ## Choose Your Filter ### Step 1 — Configured or Flexible? Configured filters cover these sensor combinations exactly: - Accel + Mag only (no gyro) - Accel + Gyro (no mag, no GPS) - Accel + Gyro + Mag - Accel + Gyro + Mag + Altimeter - Accel + Gyro + GPS (ground vehicle, no mag) - Accel + Gyro + GPS + monocular visual odometry (ground vehicle) - Accel + Gyro + Mag + GPS (synchronous rates) - Accel + Gyro + Mag + GPS (mixed rates or dropped samples) ``` Is your sensor set one of the above? │ No ─────────────────────────────────────────────────────► Step 2B (Flexible) │ Yes ▼ Need a custom motion model (constant-velocity, bicycle, etc.)? │ Yes ────────────────────────────────────────────────────► Step 2B (Flexible) │ No ▼ Need RTS smoothing, StateCovariance output, or optimizer-based tune()? │ Yes ────────────────────────────────────────────────────► Step 2B (Flexible) │ No ▼

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Choose Your Filter
  4. Step 1 — Configured or Flexible?
  5. Step 2A — Pick a configured filter
  6. Step 2B — Pick a flexible filter
  7. Data Preparation
  8. Sample Rate
  9. Time Gaps
  10. Implementation
  11. Tuning
  12. tunerconfig
  13. tunernoise Field Names by Filter
  14. Visualizing Results
Ships with 5 files
  • manifest.yaml
  • references/attitude-filters.md
  • references/inscf.md
  • references/insekf.md
  • references/navigation-filters.md
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-fuse-inertial-sensors skill do?

Analyzes sensor configurations and creates inertial fusion filters in MATLAB Navigation Toolbox. Manages filter selection (imufilter, ahrsfilter, complementaryFilter, insfilterMARG, insfilterAsync, insfilterNonholonomic, insfilterErrorState, insEKF, insCF), construction, tuning, and fusion loops. Use when fusing IMU/AHRS/INS/GPS+IMU data, estimating orientation or pose, or choosing a filter. Do NOT use for vision-only SLAM, Simulink fusion, or IMU simulation.

How do I install it?

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