pilot-service-agents-space

Retrieve NASA APOD metadata and list astronauts in space via Open Notify.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-service-agents-space
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-service-agents-space
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve NASA APOD metadata and media URLs for a given date, and list astronauts currently in space via Open Notify.

Core Features & Use Cases

  • APOD data retrieval: fetch metadata and media URLs for a given date.
  • In-space roster: list astronauts currently in space using Open Notify.
  • Workflow integration: coordinates with Pilot Protocol daemon and discovery for agent reachability.

Quick Start

Install the Pilot Protocol skill package and start using pilotctl to query space data.

Frequently Asked Questions about pilot-service-agents-space

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve NASA APOD metadata and media URLs for a specific date?

To retrieve NASA APOD metadata and media URLs for a specific date, you use pilotctl to query the service. This requires a running Pilot Protocol daemon and a reachable list-agents directory agent on the overlay to perform the authenticated data fetch.

Can I list astronauts currently in space using Open Notify data?

Yes, you can list astronauts currently in space using Open Notify. The skill queries the live roster via pilotctl, relying on the Pilot Protocol daemon and registered discovery flow to authenticate and return the active astronaut data.

Do I need a Pilot Protocol daemon running to fetch space data?

Yes, a registered Pilot Protocol daemon is required to fetch space data. The daemon must be running with pilotctl on PATH and a list-agents directory agent reachable on the overlay to execute authenticated API queries.

What is the best way to integrate space data retrieval into an existing agent workflow?

The best way to integrate space data retrieval is using the pilot-protocol core skill and pilot-service-agents discovery flow. This coordinates agent reachability across the overlay, allowing pilotctl to seamlessly fetch APOD and Open Notify data.

Why does pilotctl fail to return APOD data when queried?

pilotctl fails to return APOD data if the Pilot Protocol daemon is not running or pilotctl is not on PATH. It also fails if the list-agents directory agent is unreachable on the overlay, preventing the required authenticated API queries.

What prerequisites are needed to use the pilot-service-agents-space skill?

Prerequisites include having the pilot-protocol core skill and pilot-service-agents discovery flow installed. You also need pilotctl on PATH, a registered daemon, and a reachable list-agents directory agent on the overlay to execute queries.