Publicación en el foro

I built a Betaflight skill for Claude (AI) — blackbox decode, step-response, diff analysis. Looking for testers & feedback

Hey all,

I've been building an open-source Betaflight skill for Claude (Anthropic's AI assistant) and I'd love to get it in front of people who actually tune their own quads, because that's the only way it gets better.

It's free, Apache-2.0, and not affiliated with the Betaflight project.

The idea: instead of pasting your config into a chat and hoping the model doesn't hallucinate a parameter, the skill ships with real tooling and reference docs so Claude works from your actual artifacts — CLI

dumps, blackbox logs, and plain-language descriptions of how the quad flies.

What it can do today:

- Analyze a diff all / dump — summarizes your build (target, RX/ESC protocol, motor setup, firmware), flags anomalies and deprecated params, suggests changes with rationale (not a blind wall of set commands).

- Decode blackbox logs — it includes a pure-Python port of the official blackbox-log-viewer decoder, so it reads I/P/S frames, gives per-field stats (gyro, motor, eRPM, throttle, accelerometer) and CSV export.

Fully offline.

- Closed-loop step response — setpoint→gyro system identification via Welch cross-spectral method: rise time, overshoot %, settling time, delay, coherence, per-axis diagnosis. Best with a dedicated ID flight

(full-stick steps).

- Diagnose from symptoms — "hot motors after a flight", "wobble on hard yaw", "propwash on descent" → ranked causes + safe quick wins + what to check in the log.

- Setup wizard for a new build, and it can pull up-to-date official presets from betaflight/firmware-presets at runtime.

- Version-aware (4.4 / 4.5 / 2025.12) — flags params that would error on import to newer firmware.

Honest limitations: it's a time-domain tool — no FFT/noise spectra or filter-response plots (use blackbox.betaflight.com or PIDtoolbox for that). It defaults to 2025.12 conventions. It suggests; it never

silently applies anything.

Live FC control (preview): there's a companion MCP server (betaflight-mcp) in the works that talks to your FC over MSP — so Claude can read your PIDs/filters/rates live and, only with explicit confirmation,

write them back and save, no diff copy-pasting. It even has a guided RC-mapping detector (move a stick, it finds the channel) and switch assignment. (Status/link: [à compléter])

Safety — non-negotiable, and baked into the skill: it will never recommend disabling failsafes or arming checks, always warns before motor-direction/mapping changes, always reminds you to test props-off and in

a safe area, and never writes to a live FC without your explicit go-ahead.

How to try it:

- Claude Code: git clone into ~/.claude/skills/betaflight

- claude.ai (web/desktop/mobile): download the attached .zip from the latest release → Settings → Skills → Create skill → upload

- Repo + install details: https://github.com/SebGalina/betaflight-claude-skill

- Latest release: https://github.com/SebGalina/betaflight-claude-skill/releases/latest

What I'm looking for from you:

1. Throw a real diff all or blackbox log at it — does the analysis match what you'd conclude by hand?

2. Where does it give generic or wrong advice? Screenshots of bad answers are gold.

3. Missing parameters, version quirks, build classes (X-class, sub-250, tinywhoop) you'd want covered.

4. Anyone with a bench setup interested in testing the live MCP path when it lands.

Bug reports / ideas: GitHub issues, or just reply here. Tear it apart — that's the point. 🙏

Thanks!