skills.rest
TeoSlayer
TeoSlayerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pilot-service-agents

Discover and query the pilot-service-agents catalogue with filtering and pagination.

7|3|Updated Apr 8, 2026
Search Tags:#discovery#filters#data-access#data-sources#catalogue#pilot-protocol#service-agents
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pilot-service-agents
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-service-agents
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and query the pilot-service-agents catalogue — ~370 always-on data agents reachable over Pilot Protocol that wrap real-world APIs (Google Maps, OpenAlex, NHTSA, USGS, CoinGecko, NASA, aviation weather, and many more) so callers don't need their own API keys, rate limits, or HTTP plumbing.

Use this skill when:

  1. You need to answer a question that depends on up-to-date external data (geography, finance, aviation, science, health, academic literature, etc.) and do not want to hit the upstream APIs yourself.
  2. You want to discover which agents exist for a topic before invoking one.
  3. You want structured, paginated, filter-driven access to an upstream API without touching its SDK or auth.

Do NOT use this skill when:

  • You want agent-to-agent chat (use pilot-chat instead).
  • You are looking for swarm/task coordination (use pilot-task-router instead).
  • You need to run your own data source — these agents are consumer-side only. tags:
  • pilot-protocol
  • service-agents
  • data-sources
  • discovery
  • data-exchange license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start) and joined to the backbone (Network 0 — every daemon joins automatically at registration), which is where the catalogue lives. metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools:
    • Bash

Quick Start

Install Pilot Protocol, connect the daemon, and start querying the catalogue with list-agents to explore available service agents.

Frequently Asked Questions about pilot-service-agents

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

FAQPage Schema
How do I discover available service agents for external data APIs without managing my own API keys?▼

Use the pilot-service-agents catalogue to discover and query approximately 370 always-on data agents that wrap real-world APIs over the Pilot Protocol. Callers can filter and paginate through the catalogue to locate the right service agents without needing their own API keys or HTTP plumbing.

What prerequisites do I need to query the Pilot Protocol service agents catalogue?▼

Querying the Pilot Protocol service agents catalogue requires the pilotctl binary on your PATH and the daemon running. The daemon must be started with pilotctl daemon start and joined to the backbone where the catalogue lives, with access to the list-agents directory agent.

Can I use service agents to get structured, paginated data from upstream APIs without touching their SDK?▼

Yes, service agents provide structured, paginated, filter-driven access to upstream APIs without touching the SDK or authentication. The pilot-service-agents catalogue enables topic discovery and filtering to locate the correct agent for data access or integration tasks.

When should I not use the pilot-service-agents catalogue for data access?▼

Do not use the pilot-service-agents catalogue when you want agent-to-agent chat or swarm task coordination, as those require pilot-chat or pilot-task-router respectively. Additionally, these agents are consumer-side only and cannot run your own data source.

How do I find which data agents exist for a specific topic like finance or geography?▼

Use the pilot-service-agents catalogue to discover which agents exist for a specific topic before invoking one. It supports topic discovery and filtering across domains like geography, finance, aviation, science, health, and academic literature to locate the appropriate service agent.

Does the pilot-service-agents catalogue support filtering and pagination for locating service agents?▼

Yes, the pilot-service-agents catalogue supports filtering, pagination, and topic discovery to locate the right service agents. This allows users to efficiently navigate the approximately 370 always-on data agents available over the Pilot Protocol for data access or research tasks.

Related Skills

Explore More Data & Analytics Skills→
TeoSlayerTeoSlayer
7

pilot-service-agents-language

Translate text and access dictionaries and text-to-speech across agent networks.

Community
Advanced
TeoSlayerTeoSlayer
7

pilot-broadcast

Publish messages to all trusted peers on a topic over the Pilot Protocol network.

Community
Intermediate
TeoSlayerTeoSlayer
7

pilot-ml-training-pipeline-setup

Deploy a four-agent ML training pipeline coordinating data preparation, training, evaluation, and serving.

Community
Advanced
MacPhobosMacPhobos

MCP (Model Context Protocol) - AI-Native Server Development

Create AI-native servers exposing tools, resources, and prompts via MCP.

Community
Advanced