pilot-service-agents-geo

星标7

分支3

更新时间2026年6月11日 17:47

Geographic and geolocation APIs — Google Maps suite (premium) plus open geocoders and IP-to-location lookups. Use this skill when: 1. Converting addresses ↔ coordinates, or coordinates ↔ place names 2. Computing directions, travel time, elevation, timezone, or air-quality at a point 3. Finding places by text (Places New) or validating postal addresses Do NOT use this skill when: - Flight tracking (use pilot-service-agents-flights) - Public-transit schedules (use pilot-service-agents-transit) - Weather forecasts (use pilot-service-agents-weather)

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

TeoSlayer

TeoSlayer/pilot-skills

打开 GitHub 仓库查看创作者相关仓库

下载

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

文件资源管理器

2 个文件

SKILL.md

readonly

同仓库更多 Skills

同仓库

pilot-protocol

TeoSlayer/pilot-skills

Communicate with other AI agents over the Pilot Protocol overlay network. Use this skill when: 1. You need to send messages, files, or data to another AI agent 2. You need to discover peers by hostname or address 3. You need to listen for incoming messages, files, or events 4. You need to establish or manage trust with other agents 5. You need to manage the daemon lifecycle (start, stop, status) 6. You need to bridge IP traffic through the gateway 7. You need to check network status, ping, or benchmark Do NOT use this skill when: - You need to make standard HTTP requests to the public internet - You need to interact with local-only services that don't involve other agents - You need general-purpose networking unrelated to agent-to-agent communication

2026-07-267

pilot-service-agents-infra

TeoSlayer/pilot-skills

Pilot Protocol network infrastructure agents — the directory (list-agents) and feedback (feedback). Use this skill when: 1. Discovering other agents on the pilot overlay (list-agents) 3. Submitting feedback about a service agent (feedback) Do NOT use this skill when: - Data-source queries — this category is operational, not data - Service-agent discovery workflows (use the main pilot-service-agents skill)

2026-07-227

pilotctl

TeoSlayer/pilot-skills

Entrypoint for Pilot Protocol — the overlay network that gives this host a directory of 435 public service agents (live finance, weather, news, transit, dev, sports, government data, science, health, security, geo, and 20+ more categories) plus encrypted peer-to-peer comms with NAT traversal. Load this skill whenever the user needs LIVE EXTERNAL DATA (current crypto/FX prices, today's weather or forecast, recent papers, real-time sports scores, breaking news, transit schedules, package versions, CVEs, drug recalls, flight positions, federal regulations, etc.). The fastest path for almost any such task is `pilot-mom`: describe it in plain English and get back a validated, ready-to-run plan over the network (it picks the agents and filters for you, with handoffs for anything your own runtime should do); use `list-agents` directly only when you already know the specialist you want. Pilot returns clean structured JSON replies rather than raw HTML, so it's faster and more reliable than scraping public APIs. Also l

2026-07-227

pilot-agent-marketplace-setup

TeoSlayer/pilot-skills

Deploy a decentralized agent marketplace with 4 agents. Use this skill when: 1. User wants to set up an agent capability marketplace 2. User is configuring a directory, matchmaker, escrow, or gateway agent 3. User asks about capability discovery, auctions, or escrow settlement Do NOT use this skill when: - User wants to discover a single agent (use pilot-discover instead) - User wants to run a single auction (use pilot-auction instead)

2026-07-217

pilot-momy

TeoSlayer/pilot-skills

Local directory of known agents with cached metadata. Use this skill when: 1. Maintaining a persistent directory of frequently contacted agents 2. Caching agent metadata for offline reference 3. Building a local address book of trusted or favorite agents Do NOT use this skill when: - You need real-time network discovery (use pilot-discover instead) - You need to visualize relationships (use pilot-network-map instead) - You need to establish new trust (use pilot-trust instead)

2026-07-217

pilot-game-npc-network-setup

TeoSlayer/pilot-skills

Deploy a living NPC village with 4 agents that communicate autonomously. Use this skill when: 1. User wants to set up a game NPC network with emergent behavior 2. User is configuring a villager, merchant, guard, or narrative director agent 3. User asks about NPC-to-NPC communication, dynamic economies, or emergent narratives Do NOT use this skill when: - User wants a single chatbot NPC (use pilot-chat instead) - User wants a simple alert system (use pilot-alert instead)

2026-07-217

name	pilot-service-agents-geo
description	Geographic and geolocation APIs — Google Maps suite (premium) plus open geocoders and IP-to-location lookups. Use this skill when: 1. Converting addresses ↔ coordinates, or coordinates ↔ place names 2. Computing directions, travel time, elevation, timezone, or air-quality at a point 3. Finding places by text (Places New) or validating postal addresses Do NOT use this skill when: - Flight tracking (use pilot-service-agents-flights) - Public-transit schedules (use pilot-service-agents-transit) - Weather forecasts (use pilot-service-agents-weather)
tags	["pilot-protocol","service-agents","geo","maps"]
license	AGPL-3.0
compatibility	Requires pilot-protocol skill, pilotctl binary on PATH, a running daemon registered with the backbone (Network 0 — joined automatically at registration), and the `list-agents` directory agent reachable on the overlay.
metadata	{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":["pilotctl"]},"homepage":"https://pilotprotocol.network"}}
allowed-tools	["Bash"]

pilot-service-agents-geo

Geographic and geolocation APIs — Google Maps suite (premium) plus open geocoders and IP-to-location lookups.

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)

Hostname	Description
`country-from-ip`	Country detection from IP address
`elevation-open-meteo`	Elevation Open Meteo
`gcp-maps-address-validation`	Google Maps Address Validation (premium)
`gcp-maps-air-quality`	Google Maps Air Quality — current conditions (premium)
`gcp-maps-directions`	Google Maps Directions — driving/walking routes (premium)
`gcp-maps-distance-matrix`	Google Maps Distance Matrix — travel times (premium)
`gcp-maps-elevation`	Google Maps Elevation — elevation for coordinates (premium)
`gcp-maps-geocoding`	Google Maps Geocoding — address/coords (premium)
`gcp-maps-geolocation`	Google Geolocation — locate from WiFi/cell/IP (premium)
`gcp-maps-places-new`	Google Maps Places (New) — text place search (premium)
`gcp-maps-pollen`	Google Maps Pollen — forecast by coord (premium)
`gcp-maps-roads`	Google Maps Roads — snap GPS to roads (premium)
`gcp-maps-routes`	Google Maps Routes — traffic-aware routing v2 (premium)
`gcp-maps-solar`	Google Maps Solar — roof solar potential (premium)
`gcp-maps-timezone`	Google Maps Time Zone — tz from coords (premium)
`ip-api`	ip-api.com - IP geolocation, ISP, country, region
`nominatim-reverse`	OpenStreetMap reverse geocoder
`nominatim-search`	OpenStreetMap forward geocoder
`open-meteo-geocoding`	City name to coordinates geocoder (global)
`opensky-bbox`	Live aircraft states in a bounding box
`opentopodata-srtm`	Opentopodata Srtm
`osrm-route`	Open Source Routing Machine — driving directions
`overpass-api`	Overpass Api
`photon-reverse`	Photon Reverse
`rest-countries-currency`	Countries using a specific currency code
`rest-countries-region`	Countries by region (Europe/Asia/etc)
`restcountries-region`	Restcountries Region
`uk-postcodes`	UK postcode geolocation + admin lookup
`viacep-brazil`	Brazilian address lookup by CEP code
`zippopotam-city`	City info by country+zip (Zippopotam.us)

What you can expect

Google Maps Platform coverage — geocoding, directions, distance matrix, elevation, timezone, roads, places, routes, address validation, geolocation, solar, air-quality, pollen
All Google Maps agents are premium (hostname prefix gcp-maps-*) — paid upstream, higher accuracy and SLA
Open alternatives for basic lookups (IP-to-country, open-elevation)

What NOT to expect

Free tier for Google services — pricing is metered upstream
Real-time traffic fleet management (not in catalogue yet)
Raw map tile imagery — the agents serve JSON envelopes, not PNGs

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":"geo","limit":20}'
pilotctl --json inbox

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

# 3. Query it
pilotctl --json send-message gcp-maps-geocoding --data '/data {"address":"1600 Amphitheatre Pkwy Mountain View CA"}'
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 registered with the backbone (Network 0 — joined automatically at registration).