Pilot Service Agents Government

v1.0.0

Government and civic data — federal register, FBI wanted, elections info, national open-data portals. Use this skill when: 1. Finding current US federal regu...

0· 44·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-government.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pilot Service Agents Government" (teoslayer/pilot-service-agents-government) from ClawHub.
Skill page: https://clawhub.ai/teoslayer/pilot-service-agents-government
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-government

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-service-agents-government
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description map directly to the actions the SKILL.md instructs (discover/list agents, send '/data', '/help', '/summary' via pilotctl). Requiring pilotctl and a pilot-protocol daemon joined to the network is coherent for a skill that queries an overlay of service agents.
Instruction Scope
The instructions require operating a local pilot-protocol daemon joined to network 9 and communicating with remote overlay agents (list-agents, sending messages, reading the inbox). This is within the claimed purpose but means queries are sent over an external overlay—users should avoid sending sensitive secrets in queries. The SKILL.md does not instruct reading local files or environment variables beyond using pilotctl.
Install Mechanism
Instruction-only skill with no install spec or code files. No downloads or archive extraction; lowest install risk. It does require an external binary (pilotctl) which must already be present/trusted on PATH.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The mention of 'premium gcp-civic-elections' is descriptive of an upstream agent and does not translate into required local credentials in this skill.
Persistence & Privilege
always is false and agent invocation is normal (not disabled). The skill does not request permanent presence or system-wide config changes. It simply instructs use of pilotctl to communicate with overlay agents.
Assessment
This skill is coherent for querying government/civic data via the Pilot Protocol overlay, but exercise caution before use: 1) Install pilotctl only from an official/trusted source and ensure the pilot-protocol daemon you run is trustworthy. 2) Joining the overlay (network 9) means your queries go to remote peers—do not include private tokens, passwords, or sensitive PII in requests. 3) Verify agent contracts with '/help' before sending data and confirm any upstream 'premium' agents require separate credentials. 4) If you have privacy concerns, run the daemon in an isolated environment or test with non-sensitive queries first.

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

Runtime requirements

Binspilotctl
latestvk9797qj92gkff88svy5ctpnn9n85qjpa
44downloads
0stars
1versions
Updated 20h ago
v1.0.0
MIT-0

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)

HostnameDescription
brazil-api-banksBrazilian banks directory
brazil-api-cepBrazilian ZIP/CEP postal code lookup
canadian-gov-datasetsCanadian Gov Datasets
fbi-wantedFBI wanted persons list
federal-registerUS Federal Register documents
gcp-civic-electionsGoogle Civic Info election directory
noaa-alerts-activeNWS active US weather alerts (GeoJSON)
nobel-prize-laureatesNobel Prize laureates across all fields
singapore-psi-airSingapore PSI/air quality reading
singapore-weather-24hSingapore 24-hour weather forecast
uk-parliament-membersUK Parliament members search
uk-police-crimesUK street-level crime data
us-census-populationUS Census ACS population data
usaspending-agenciesUS federal spending by agency
weather-gov-stationsWeather Gov Stations
world-bank-healthWorld Bank health expenditure indicator
worldbank-income-levelsWorldbank Income Levels
worldbank-lending-typesWorldbank Lending Types
worldbank-projectsWorldbank Projects
worldbank-regionsWorldbank Regions
worldbank-sourcesWorldbank Sources
worldbank-topicsWorldbank 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 joined to network 9.

Comments

Loading comments...