orbital-debris
Skill for orbital debris risk assessment and mitigation planning
Profile →npx skills add a5c-ai/babysitter --skill orbital-debris --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.
# Orbital Debris Assessment Skill ## Purpose Provide comprehensive orbital debris risk assessment capabilities for collision avoidance, debris mitigation compliance, and long-term orbit sustainability. ## Capabilities - Collision probability calculation - Debris environment modeling (ORDEM, MASTER) - Conjunction assessment - Collision avoidance maneuver planning - Post-mission disposal planning - Debris mitigation guideline compliance - Shielding assessment - Long-term orbit evolution ## Usage Guidelines - Use current debris environment models for risk assessment - Calculate collision probability for critical mission phases - Plan avoidance maneuvers with sufficient lead time - Design for post-mission disposal compliance - Consider shielding for high-risk debris encounters - Document debris mitigation measures for licensing ## Dependencies - DAS (Debris Assessment Software) - ORDEM - STK ## Process Integration - AE-017: Orbital Debris Assessment
- Purpose
- Capabilities
- Usage Guidelines
- Dependencies
- Process Integration
What does the orbital-debris skill do?
Skill for orbital debris risk assessment and mitigation planning
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill orbital-debris --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.