Pilot service agents government

Skill TeoSlayer/pilot-skills/skills/pilot-service-agents-government

80+ agent skills for Pilot Protocol — communication, file transfer, trust, task routing, swarm coordination, and more

Install

npx -y skills add TeoSlayer/pilot-skills --skill pilot-service-agents-government

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Government and civic data — federal register, FBI wanted, elections info, national open-data portals. Use this skill when: 1. Finding current US federal regulations or notices (Federal Register) 2. Looking up civic info: elections, polling, representatives (Google Civic Info) 3. Searching national open-data catalogs (data.gov.br, Canadian CKAN, etc.) Do NOT use this skill when: - Financial filings (use pilot-service-agents-gov-finance for SEC/BLS) - Tariff lookups (use pilot-service-agents-gov-finance — `hts-usitc-search`) - Health statistics (use pilot-service-agents-health for CDC/WHO)

The file declares its own license as AGPL-3.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.0 KB, as published. Nobody here has run it

pilot-service-agents-government

Government and civic data — federal register, FBI wanted, elections info, national open-data portals.

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
`brazil-api-banks`	Brazilian banks directory
`brazil-api-cep`	Brazilian ZIP/CEP postal code lookup
`canadian-gov-datasets`	Canadian Gov Datasets
`fbi-wanted`	FBI wanted persons list
`federal-register`	US Federal Register documents
`gcp-civic-elections`	Google Civic Info election directory
`noaa-alerts-active`	NWS active US weather alerts (GeoJSON)
`nobel-prize-laureates`	Nobel Prize laureates across all fields
`singapore-psi-air`	Singapore PSI/air quality reading
`singapore-weather-24h`	Singapore 24-hour weather forecast
`uk-parliament-members`	UK Parliament members search
`uk-police-crimes`	UK street-level crime data
`us-census-population`	US Census ACS population data
`usaspending-agencies`	US federal spending by agency
`weather-gov-stations`	Weather Gov Stations
`world-bank-health`	World Bank health expenditure indicator
`worldbank-income-levels`	Worldbank Income Levels
`worldbank-lending-types`	Worldbank Lending Types
`worldbank-projects`	Worldbank Projects
`worldbank-regions`	Worldbank Regions
`worldbank-sources`	Worldbank Sources
`worldbank-topics`	Worldbank Topics

What you can expect

US and international civic/regulatory sources — Federal Register, FBI Wanted, Brazilian CEP + banks, Canadian open-data
Google Civic Information (elections, polling locations) — premium gcp-civic-elections
Structured filter-based search; /help on each agent shows the fields

What NOT to expect

Political commentary or news (use news category)
Worldwide coverage — each agent is country-specific

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

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

# 3. Query it
pilotctl --json send-message federal-register --data '/data {"term":"clean air act","per_page":5}'
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).