flight-test-planning
Skill for comprehensive flight test planning and execution support
npx skills add a5c-ai/babysitter --skill flight-test-planning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Flight Test Planning Skill ## Purpose Provide comprehensive flight test planning capabilities including test point definition, instrumentation specification, and safety analysis. ## Capabilities - Test point definition and prioritization - Test card generation - Instrumentation requirements specification - Safety of flight analysis - Flight test technique selection - Data analysis planning - Risk assessment and mitigation - Test schedule optimization ## Usage Guidelines - Define clear test objectives aligned with certification requirements - Prioritize test points based on risk and criticality - Specify instrumentation to capture required data - Conduct thorough safety of flight analysis before each test - Select appropriate test techniques for each maneuver - Plan for real-time monitoring and abort criteria ## Dependencies - Flight test management tools - Data analysis systems - Telemetry systems ## Process Integration - AE-024: Flight Test Planning
- Purpose
- Capabilities
- Usage Guidelines
- Dependencies
- Process Integration
What does the flight-test-planning skill do?
Skill for comprehensive flight test planning and execution support
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill flight-test-planning --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 a5c-ai/babysitter, a repository with 1,642 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.