spacex
CLI for AI agents to lookup SpaceX launches and rockets for their humans. No auth required.
Best use case
spacex is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
CLI for AI agents to lookup SpaceX launches and rockets for their humans. No auth required.
Teams using spacex should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/spacex/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How spacex Compares
| Feature / Agent | spacex | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
CLI for AI agents to lookup SpaceX launches and rockets for their humans. No auth required.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SpaceX Lookup
CLI for AI agents to lookup SpaceX launches, rockets, and crew for their humans. "When's the next SpaceX launch?" — now your agent can answer.
Uses the community SpaceX API. No account or API key needed.
## Usage
```
"What are the upcoming SpaceX launches?"
"Show me the last 5 SpaceX launches"
"Tell me about the Falcon 9"
"Who are the SpaceX crew members?"
```
## Commands
| Action | Command |
|--------|---------|
| Upcoming launches | `spacex launches upcoming [limit]` |
| Past launches | `spacex launches past [limit]` |
| Launch details | `spacex launch <id>` |
| List rockets | `spacex rockets` |
| Rocket details | `spacex rocket <id>` |
| Crew members | `spacex crew [limit]` |
### Examples
```bash
spacex launches # Next 10 upcoming launches
spacex launches upcoming 5 # Next 5 upcoming launches
spacex launches past 5 # Last 5 launches
spacex launch 5eb87d47ffd86e000604b38a # Full launch details
spacex rockets # All rockets
spacex rocket 5e9d0d95eda69973a809d1ec # Falcon 9 details
spacex crew 5 # First 5 crew members
```
## Output
**Launch list output:**
```
🚀 Starlink 4-36 (v1.5) — Falcon 9, 2022-10-20, Cape Canaveral
```
**Launch detail output:**
```
🚀 SAOCOM 1B, GNOMES-1, Tyvak-0172
ID: 5eb87d47ffd86e000604b38a
Flight #: 101
Date: 2020-08-30 (hour)
Rocket: Falcon 9
Launchpad: Cape Canaveral
Status: ✅ Success
📋 Details:
[Full mission description]
🎥 Webcast: https://youtu.be/P-gLOsDjE3E
📚 Wikipedia: https://en.wikipedia.org/wiki/SAOCOM
```
**Rocket list output:**
```
🛸 Falcon 9 — rocket, 2010-06-04, Active, 98% success
```
**Crew output:**
```
👨🚀 Robert Behnken — NASA, active
```
## Notes
- Uses SpaceX API v4 (api.spacexdata.com)
- No authentication required
- Data may lag behind real-time (community maintained)
- Rockets: Falcon 1, Falcon 9, Falcon Heavy, Starship
- Launchpads: Cape Canaveral, Vandenberg, Boca Chica, Kwajalein
---
## Agent Implementation Notes
**Platform note:** If your human is on Windows, they'll need WSL, Git Bash, or Cygwin to run this skill.
**Script location:** `{skill_folder}/spacex` (wrapper to `scripts/spacex`)
**When user asks about SpaceX:**
1. Run `./spacex launches` for upcoming launches
2. Run `./spacex launches past` for recent launches
3. Run `./spacex launch <id>` for full mission details
4. Run `./spacex rockets` for rocket info
**Common queries:**
- "Next SpaceX launch" → `spacex launches upcoming 1`
- "Recent launches" → `spacex launches past 5`
- "Falcon 9 specs" → `spacex rockets` then `spacex rocket <id>`
- "SpaceX crew" → `spacex crew`
**Don't use for:** Non-SpaceX launches (NASA, Blue Origin, etc.)Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
accessibility-ux-audit
Audit and enhance accessibility and UX across all pages and components.
accessibility-testing
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
accessibility-rules
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
accessibility-planning
Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.
accessibility-design
WCAG 2.1 AA compliance patterns, screen reader compatibility, keyboard navigation, and ARIA best practices. Use when implementing accessible interfaces, reviewing UI components, or auditing accessibility compliance. Covers semantic HTML, focus management, color contrast, and assistive technology testing.
accessibility-design-checklist
Эксперт по accessibility дизайну. Используй для WCAG, a11y чеклистов и inclusive design.
accessibility-design-checker
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
accessibility-contrast-audit
[Design System] Quantitative accessibility audit for UI - contrast ratios, font sizes, tap targets, heading hierarchy. Use when (1) checking WCAG color contrast compliance, (2) auditing text sizes for readability, (3) validating touch/click target sizes, (4) reviewing heading structure and landmarks, (5) user asks to 'check accessibility', 'audit contrast', 'WCAG compliance', or 'a11y check'.
accessibility-compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
accessibility-by-default
Treats accessibility as a baseline requirement, not a feature. WCAG 2.1/2.2 AA principles embedded into every decision.
accessibility-basic-check
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.