Pilot service agents gov finance
Skill TeoSlayer/pilot-skills/skills/pilot-service-agents-gov-finance
Government economic and financial records — SEC EDGAR, BLS time series, HTS/USITC tariffs, US Dept of Ed. Use this skill when: 1. Pulling SEC EDGAR XBRL company facts or recent submissions for a CIK 2. Bureau of Labor Statistics time-series lookup 3. HTS/USITC tariff classification search Do NOT use this skill when: - Market prices / trading data (use pilot-service-agents-finance) - Macro indicators (use pilot-service-agents-economics)From its SKILL.md
npx -y skills add TeoSlayer/pilot-skills --skill pilot-service-agents-gov-financeAssembled 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 file declares
Copied from the file, not written here
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
3.7 KB, 733 tokens by cl100k_base, as published. Nobody here has run it
pilot-service-agents-gov-finance
Government economic and financial records — SEC EDGAR, BLS time series, HTS/USITC tariffs, US Dept of Ed.
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 |
|---|---|
bls-timeseries | BLS time series data |
data-ed-gov | US Dept of Education (CKAN) |
hts-usitc-search | HTS tariff search |
sec-company-facts | SEC EDGAR XBRL company facts |
sec-submissions | SEC EDGAR submissions for a CIK |
What you can expect
- Regulatory-grade primary sources (SEC, BLS, USITC)
- Structured responses tied to official identifiers (CIK, series IDs, HTS codes)
What NOT to expect
- Real-time trade reports
- Non-US regulatory filings
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":"gov-finance","limit":20}'
pilotctl --json inbox
# 2. Read the contract of a specific agent
pilotctl --json send-message sec-company-facts --data '/help'
pilotctl --json inbox
# 3. Query it
pilotctl --json send-message sec-company-facts --data '/data {"cik":"0000320193"}'
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).
What ships with it: 1 file
965 B alongside SKILL.md
- README.md965 B
Gives 0 of the 12 instructions most finance skills give in 733 tokens
Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07
- Extract date vendor amount and descriptionin 15 of 469, across 3 files
- Scan folder for invoice filesin 14 of 469, across 2 files
- Rename files to standard formatin 14 of 469, across 2 files
- Show organization plan before movingin 14 of 469, across 2 files
- Generate summary CSVin 14 of 469, across 2 files
- Organize files by categoryin 13 of 469, across 1 file
- Preserve original filesin 13 of 469, across 1 file
- Flag files missing critical infoin 13 of 469, across 1 file
- Produce the requested output filein 9 of 469, across 4 files
- Build best, base, and worst case scenariosin 9 of 469, across 5 files
- Implement backoff if rate limit errors occurin 8 of 469, across 3 files
- Determine the weighted average cost of capitalin 8 of 469, across 4 files
Said here and by no other author read
- Verify agents with a fresh list-agents query
- Do not hard-code the agent catalogue
- Send /help to read an agent filter schema
- Send /data with json filters for structured data
- Send /summary with json filters for natural-language summaries
- Read the actual agent response from the inbox
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.