Pilot Service Agents Health

v1.0.0

Public-health and biomedical APIs — ClinicalTrials.gov, openFDA, CDC, WHO, ClinVar, DailyMed, disease.sh. Use this skill when: 1. Searching active/past clini...

0· 37·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-health.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-service-agents-health
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions: all operations use the pilotctl CLI and Pilot Protocol network to discover and query health-data agents. Requiring pilotctl and the pilot-protocol core skill is appropriate for this functionality.
Instruction Scope
SKILL.md only instructs the agent to use pilotctl to list agents, read agent contracts (/help), send /data and /summary requests, and read the protocol inbox. It does not ask for unrelated files, system credentials, or private data; it explicitly forbids PHI and medical-advice usage.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk install footprint. It assumes an existing pilotctl binary on PATH and a running Pilot Protocol daemon, which is reasonable for the declared protocol integration.
Credentials
The skill requests no environment variables, credentials, or config paths. This is proportionate given it communicates via the pilotctl CLI and relies on the daemon/overlay for connectivity.
Persistence & Privilege
The skill is not marked always:true and does not request persistent or elevated system privileges. It does not modify other skills' configuration or require system-wide changes.
Assessment
This skill appears coherent and focused on querying public health agents over the Pilot Protocol. Before installing, verify you trust the pilotctl binary and the Pilot Protocol daemon you will join (network 9), since network membership can expose metadata and allow agent-to-agent messaging. Inspect the pilot-protocol and pilot-service-agents core skills (and any 'list-agents' directory agent) to confirm they come from trusted sources. Do not use this skill for PHI or giving medical advice; when using /summary note that the agent may produce LLM-generated prose (confirm where that LLM runs and whether data is sent to an external service if that matters to you).

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

Runtime requirements

Binspilotctl
latestvk97f8bwvqds92rg0a0ttzesmv185pv3a
37downloads
0stars
1versions
Updated 12h ago
v1.0.0
MIT-0

pilot-service-agents-health

Public-health and biomedical APIs — ClinicalTrials.gov, openFDA, CDC, WHO, ClinVar, DailyMed, disease.sh.

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
cdc-covid-vaxCDC COVID-19 vaccination data by jurisdiction
clinicaltrials-searchClinicalTrials.gov v2 studies search
clinvar-esearchClinvar Esearch
dailymed-splDailymed Spl
disease-sh-countriesCOVID-19 per-country live statistics
disease-sh-coviddisease.sh COVID-19 country statistics
mesh-lookupMesh Lookup
ncbi-gene-esearchNcbi Gene Esearch
ncbi-pubmed-esearchNcbi Pubmed Esearch
noaa-tidesNOAA Tides & Currents water level data
open-disease-covidCOVID-19 and flu live global counts
openfda-adverse-eventsOpenfda Adverse Events
openfda-device-eventFDA medical device adverse event reports
openfda-drugopenFDA drug label search - FDA-approved drug data
openfda-drug-eventsopenFDA drug adverse event reports
openfda-food-recallFDA food product recall enforcement reports
openfda-ndcOpenfda Ndc
openfdadevice-recallOpenfdadevice Recall
pubmed-esearch-v2PubMed article metadata by PMID
rxnorm-drugRxNorm drug name/ingredient lookup (NIH/NLM)
rxnorm-drugsRxnorm Drugs
wger-exercisesExercise/workout database with muscle groups
who-disease-outbreaksWho Disease Outbreaks
who-gho-data-life-expectWho Gho Data Life Expect
who-gho-data-mortalityWho Gho Data Mortality
who-gho-indicatorWHO Global Health Observatory indicators
who-gho-indicators-listWho Gho Indicators List

What you can expect

  • Regulatory and surveillance data — FDA drug labels, CDC indicators, disease.sh country COVID stats
  • ClinicalTrials.gov v2 study search with rich filters
  • WHO Global Health Observatory (mortality, life-expectancy, disease outbreaks)

What NOT to expect

  • Personal health records — all data is anonymised/public
  • Diagnostic advice — outputs are raw structured records
  • Live provider directories (not in catalogue)

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

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

# 3. Query it
pilotctl --json send-message clinicaltrials-search --data '/data {"query":"sleep apnea","status":"RECRUITING"}'
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...