How do I install the Run Configurator skill?

Run npx skillmds@latest add sensei-hacker/run-configurator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Run Configurator skill do?

Launch INAV Configurator in development mode for testing It is listed under Coding & Dev Tools on SkillMD.

Is Run Configurator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Run Configurator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Run Configurator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Run Configurator?

sensei-hacker (@sensei-hacker) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Run Configurator by sensei-hacker — Agent Skill

Name: Run Configurator
Author: sensei-hacker

File contents

Run INAV Configurator

Launch the INAV Configurator desktop application in development mode for testing changes.

Quick Start

cd inav-configurator
ENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222

This launches the Electron app in development mode with hot-reload enabled.

Running in Background

If you need to continue working while the configurator runs:

cd inav-configurator
ENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222 &

Or use the Bash tool with run_in_background: true parameter.

Why NODE_ENV=development?

The NODE_ENV=development environment variable:

Enables development features and debugging
Enables hot-reload for faster iteration
May show additional console logging
Required for proper development mode operation

Common Issues

Problem	Solution
`npm start` fails	New installations: Run `npm install` first to ensure dependencies are installed
Missing NODE_ENV warning	Always use `ENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222`
Port already in use	Another instance may be running - check with `ps aux \| grep electron`
Changes not reflected	The app should hot-reload, but you may need to restart

Development Workflow

Make changes to configurator code
Run configurator to test changes: ENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222 &
The app should automatically reload when files change
Check browser console (Ctrl+Shift+I / Cmd+Option+I) for errors

Stopping the Configurator

If running in foreground: Press Ctrl+C in the terminal
If running in background: pkill -f "electron.*configurator" or use the app's quit button

Building for Distribution

This skill runs the configurator in development mode. To create distributable packages:

cd inav-configurator
npm run package  # Package the app
npm run make     # Create installers

Related Skills

build-sitl - Build SITL firmware to test with configurator
test-crsf-sitl - Complete CRSF telemetry testing workflow (uses configurator for setup)
sitl-arm - Arm SITL for testing (often used with configurator)
pr-review - Test configurator PRs locally using this skill

---name: run-configuratordescription: Launch INAV Configurator in development mode for testing---# Run INAV ConfiguratorLaunch the INAV Configurator desktop application in development mode for testing changes.## Quick Start```bashcd inav-configuratorENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222```This launches the Electron app in development mode with hot-reload enabled.## Running in BackgroundIf you need to continue working while the configurator runs:```bashcd inav-configuratorENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222 &```Or use the Bash tool with `run_in_background: true` parameter.## Why NODE_ENV=development?The `NODE_ENV=development` environment variable:- Enables development features and debugging- Enables hot-reload for faster iteration- May show additional console logging- Required for proper development mode operation## Common Issues| Problem | Solution ||---------|----------|| `npm start` fails | New installations: Run `npm install` first to ensure dependencies are installed || Missing NODE_ENV warning | Always use `ENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222` || Port already in use | Another instance may be running - check with `ps aux \| grep electron` || Changes not reflected | The app should hot-reload, but you may need to restart |## Development Workflow1. Make changes to configurator code2. Run configurator to test changes: `ENABLE_REMOTE_DEBUGGING=1 NODE_ENV=development npm start --remote-debugging-port=9222 &`3. The app should automatically reload when files change4. Check browser console (Ctrl+Shift+I / Cmd+Option+I) for errors## Stopping the Configurator- If running in foreground: Press Ctrl+C in the terminal- If running in background: `pkill -f "electron.*configurator"` or use the app's quit button## Building for DistributionThis skill runs the configurator in development mode. To create distributable packages:```bashcd inav-configuratornpm run package # Package the appnpm run make # Create installers```---## Related Skills- **build-sitl** - Build SITL firmware to test with configurator- **test-crsf-sitl** - Complete CRSF telemetry testing workflow (uses configurator for setup)- **sitl-arm** - Arm SITL for testing (often used with configurator)- **pr-review** - Test configurator PRs locally using this skill

Frequently asked questions

Run Configurator