AI SummaryThis skill helps users configure, tune, troubleshoot, and analyze Betaflight-based FPV drone setups. Betaflight is the dominant open-source firmware for multirotor flight controllers, and configurations are expressed through CLI commands () that can be dumped, edited, and replayed. When in doubt, ap
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "betaflight" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/betaflight-claude-skill && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/betaflight-claude-skill/SKILL.md "https://raw.githubusercontent.com/SebGalina/betaflight-claude-skill/main/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Use whenever the user mentions Betaflight, FPV drone firmware, flight-controller config, PID/filter/rates tuning, or blackbox log analysis — or shares a Betaflight artifact: a CLI diff/dump (lines like 'diff all', 'set ', 'feature ', 'resource ') or a .bbl/.bfl blackbox log, even when not named as such — or runs a chirp tuning session via Sweep Studio / FPVLogForge (a chirp log ID to analyse, 'analyse log', 'résultat chirp', iterative Bode/step/Ms tuning). Covers flight symptoms (oscillations, wobble, propwash, jello, hot motors, drift), motor/ESC and RX/ELRS/CRSF setup, builds from 3" to 10" (cinewhoop, tinywhoop, longrange, X-class), version migrations (4.4 → 4.5 → 4.6), and configuring a new drone from scratch (setup wizard). Trigger even when phrased casually ("mon drone wobble", "PID help", "config FC") — under-triggering is worse than over-triggering.
Betaflight Assistant
This skill helps users configure, tune, troubleshoot, and analyze Betaflight-based FPV drone setups. Betaflight is the dominant open-source firmware for multirotor flight controllers, and configurations are expressed through CLI commands (set xxx = yyy) that can be dumped, edited, and replayed.
When this skill applies
• The user asks anything about Betaflight, even tangentially (Configurator, CLI, PIDs, filters, rates, RX/ELRS/CRSF, ESC protocols, motors, blackbox). • The user shares or pastes content that looks like Betaflight CLI output (lines starting with set , feature , resource , serial , diff all, dump). • The user shares a blackbox log file (.bbl, .bfl, .txt with header H Product:Blackbox flight data recorder). • The user describes a flight issue typical of Betaflight tuning: oscillations, propwash, jello, hot motors, drift, yaw spin, failsafes, RX dropouts. • The user mentions specific Betaflight versions (4.4, 4.5, 4.6) or asks about migrating between them. • The user wants to configure a new drone from scratch → launch the setup wizard (see below). When in doubt, apply this skill — under-triggering is a worse failure mode than over-triggering here. > Wizard hint — mention to the user that they can say _"configure from scratch"_, _"nouveau drone"_, _"wizard"_, or _"partir de zéro"_ to launch the guided setup wizard.
Core workflow
> Script execution rule: when the user shares a file, always execute the relevant script — never analyse the file manually or answer from memory alone. If the code-execution tool is unavailable, tell the user to enable it (Claude Desktop: conversation settings → Analysis tool) before proceeding. • Identify the artifact type the user is providing: • FC plugged in + MCP server available → read live via the MCP tools (see "MCP integration" below) — takes priority over everything else • CLI diff/dump (text file or pasted block) → execute python -m scripts.parse_diff on it • Blackbox log (.bbl/.bfl) → execute python -m scripts.analyze_blackbox on it (full frame decode on demand) • Description of flight behavior with no file → diagnostic interview • No artifact, generic question → answer from references/ • Read the relevant reference file before answering specific questions: • PID/filter/rates questions → references/pid-tuning.md (fallback: pid-tuning.md) • CLI command syntax → references/cli-commands.md (fallback: cli-commands.md) • Specific set parameters → references/parameters.md (fallback: parameters.md) • Flight symptoms → references/troubleshooting.md (fallback: troubleshooting.md) • Arming failures / arming flags → references/arming-flags.md (fallback: arming-flags.md) • USB driver / MCU / COM port not found → references/mcu-usb-drivers.md (fallback: mcu-usb-drivers.md) • Version differences → references/version-changes.md (fallback: version-changes.md) • Diagnose, don't guess. If symptoms are ambiguous, ask one or two targeted questions (frame size, motor KV, prop, battery, firmware version) before recommending changes. • Recommend changes as CLI snippets the user can paste directly into Betaflight Configurator's CLI tab. Always wrap them in a code block and end with save.
MCP integration — live FC
When the betaflight-mcp server is available, always prefer a live read over asking for a diff. Mandatory pattern: read → compute → confirm → write → save_config. Never call save_config without explicit confirmation — it reboots the FC. Detection: try list_serial_ports; if it responds, the server is active. Otherwise fall back to offline mode (CLI diff) without blocking. → Full tool catalogue, write pattern, and error handling: references/mcp-tools.md
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster