WORKFLOW / discovery-4306022957c5b91cad288720

Compare drone tuning changes using recorded chirp logs

# Compare drone tuning changes using recorded chirp logs

ID: discovery-4306022957c5b91cad288720
Category: Creativity & hobbies
Reported agent: Claude
Evidence: Setup guide
Source: [GitHub](https://github.com/SebGalina/betaflight-claude-skill)
Last reviewed: 2026-11-12

The Betaflight skill documents Claude turning existing chirp logs into an offline report with frequency response, step response, gyro noise and before/after comparisons.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

## Connections and alternatives

- Attach one existing CHIRP log for a single-pass report.
- Supply before/after logs in chronological order with notes on changed settings.

## Workflow steps

- Inspect log headers, firmware, sessions and settings. Confirm these are CHIRP identification logs and keep originals unchanged.
- Run the documented chirp_analysis workflow into a new HTML report. For a fixed comparison, use only the supplied logs in oldest-to-newest order.
- Inspect sweep sanity and coherence before comparing per-axis response, noise, motor harmonics and setting changes.
- Return the report, measured differences and uncertain conclusions. Do not modify flight-controller settings or initiate a flight.

## Expected result

An offline tuning-comparison report grounded in the selected recorded flights.

## Limitations

Documented capability, not independently tested. Poor excitation or coherence weakens conclusions; a score does not establish flight safety. The source warns never to enable CHIRP on the ground.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Compare drone tuning changes using recorded chirp logs

MY SETUP
- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Inspect log headers, firmware, sessions and settings. Confirm these are CHIRP identification logs and keep originals unchanged.
2. Run the documented chirp_analysis workflow into a new HTML report. For a fixed comparison, use only the supplied logs in oldest-to-newest order.
3. Inspect sweep sanity and coherence before comparing per-axis response, noise, motor harmonics and setting changes.
4. Return the report, measured differences and uncertain conclusions. Do not modify flight-controller settings or initiate a flight.

EXPECTED RESULT
An offline tuning-comparison report grounded in the selected recorded flights.

LIMITATIONS
Documented capability, not independently tested. Poor excitation or coherence weakens conclusions; a score does not establish flight safety. The source warns never to enable CHIRP on the ground.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

Documented capability, not independently tested. Poor excitation or coherence weakens conclusions; a score does not establish flight safety. The source warns never to enable CHIRP on the ground. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.

## Stored structured recipe

{
"goal": "Compare drone tuning changes using recorded chirp logs",
"sources": [
"Attach one existing CHIRP log for a single-pass report.",
"Supply before/after logs in chronological order with notes on changed settings."
],
"access": "Claude with the Betaflight skill release installed, or Claude Code with Python dependencies; Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context",
"trigger": "On demand",
"steps": [
"Inspect log headers, firmware, sessions and settings. Confirm these are CHIRP identification logs and keep originals unchanged.",
"Run the documented chirp_analysis workflow into a new HTML report. For a fixed comparison, use only the supplied logs in oldest-to-newest order.",
"Inspect sweep sanity and coherence before comparing per-axis response, noise, motor harmonics and setting changes.",
"Return the report, measured differences and uncertain conclusions. Do not modify flight-controller settings or initiate a flight."
],
"output": "An offline tuning-comparison report grounded in the selected recorded flights.",
"guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
"sourceNotes": "The Betaflight skill documents Claude turning existing chirp logs into an offline report with frequency response, step response, gyro noise and before/after comparisons.",
"sourceStatus": "documented capability",
"generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

## Connections

- Attach one existing CHIRP log for a single-pass report.
- Supply before/after logs in chronological order with notes on changed settings.

## Steps

## Starter request

TASK: Compare drone tuning changes using recorded chirp logs

MY SETUP
- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

EXPECTED RESULT
An offline tuning-comparison report grounded in the selected recorded flights.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

## Connections

- Attach one existing CHIRP log for a single-pass report.
- Supply before/after logs in chronological order with notes on changed settings.

## Steps

## Starter request

TASK: Compare drone tuning changes using recorded chirp logs

MY SETUP
- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

EXPECTED RESULT
An offline tuning-comparison report grounded in the selected recorded flights.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

## Connections

- Attach one existing CHIRP log for a single-pass report.
- Supply before/after logs in chronological order with notes on changed settings.

## Steps

## Starter request

TASK: Compare drone tuning changes using recorded chirp logs

MY SETUP
- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

EXPECTED RESULT
An offline tuning-comparison report grounded in the selected recorded flights.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

## Connections

- Attach one existing CHIRP log for a single-pass report.
- Supply before/after logs in chronological order with notes on changed settings.

## Steps

## Starter request

TASK: Compare drone tuning changes using recorded chirp logs

MY SETUP
- Claude with the Betaflight skill release installed, or Claude Code with Python dependencies
- Previously recorded, compatible Betaflight CHIRP blackbox logs and configuration context

EXPECTED RESULT
An offline tuning-comparison report grounded in the selected recorded flights.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-4306022957c5b91cad288720