Pilot Service Agents Space

v1.0.0

Space and astronomy — NASA Astronomy Picture of the Day, Open Notify astronauts. Use this skill when: 1. Fetching APOD metadata + media URLs for a given date...

0· 21·0 current·0 all-time
byCalin Teodor@teoslayer

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for teoslayer/pilot-service-agents-space.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pilot Service Agents Space" (teoslayer/pilot-service-agents-space) from ClawHub.
Skill page: https://clawhub.ai/teoslayer/pilot-service-agents-space
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: pilotctl
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install pilot-service-agents-space

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-service-agents-space
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the required artifacts: the skill is explicitly a pilot-protocol client that needs pilotctl, a running pilot daemon on network 9, and the list-agents directory. Those requirements are proportionate to a skill that queries overlay service agents.
Instruction Scope
SKILL.md only instructs the agent to run pilotctl send-message and pilotctl inbox to discover agents, read /help, request /data or /summary, and parse returned envelopes. It does not instruct reading unrelated system files or environment variables. Note: responses include an upstream_url field (resolved external media URLs) — the agent will surface external links/media returned by upstream services.
Install Mechanism
Instruction-only skill with no install spec or code files; no downloads or archive extracts. Lowest-risk install profile (relies on existing pilotctl binary and pilot-protocol daemon).
Credentials
No environment variables, credentials, or config paths are requested. The declared requirements (pilotctl binary, pilot-protocol daemon, network 9 membership) are consistent with the skill's function.
Persistence & Privilege
always is false and the skill is user-invocable; model invocation is allowed (default) but there are no indicators the skill requests elevated or persistent system privileges or modifies other skills or system settings.
Assessment
This skill is a simple client guide for using pilotctl to query two service agents (NASA APOD and Open Notify). Before installing: ensure you trust the pilot-protocol implementation and pilotctl binary you will run; running and joining a peer overlay (network 9) involves network exposure—use an environment you control if you are uncertain. Be aware responses may include resolved external media URLs (upstream_url) — treat links/media cautiously. No secrets are requested by this skill.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binspilotctl
latestvk972ynxh3een24q1bm5zygc8z185qvg3
21downloads
0stars
1versions
Updated 6h ago
v1.0.0
MIT-0

pilot-service-agents-space

Space and astronomy — NASA Astronomy Picture of the Day, Open Notify astronauts.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)

HostnameDescription
nasa-apodNASA Astronomy Picture of the Day
open-notify-astrosAstronauts currently in space

What you can expect

  • Two very specific lightweight sources, both free and low-rate

What NOT to expect

  • Deep astronomy catalogs (SIMBAD, VizieR) — not yet wrapped

Commands (same pattern for every agent in the category)

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape

send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"space","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message nasa-apod --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message nasa-apod --data '/data {"date":"2025-07-04"}'
pilotctl --json inbox

Dependencies

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.

Comments

Loading comments...