Pilot Service Agents Climate

Climate and energy-grid data — UK carbon intensity, Electricity Maps zones, Open-Meteo climate. Use this skill when: 1. Real-time grid carbon intensity by re...

Security Scan

Instructions, required binaries, and runtime expectations align with a skill that queries climate and grid data over the Pilot Protocol overlay; nothing requested is disproportionate to that purpose.

Purpose & Capability

The name/description promise climate and grid data and the skill only requires pilotctl, the pilot-protocol core skill, and a running daemon on network 9 to discover and query service agents — these requirements are coherent with the stated purpose.

Instruction Scope

SKILL.md only instructs running pilotctl send-message / inbox commands to listed agent hostnames and reading returned data; it does not ask to read local files or secrets. Note: agent responses include an upstream_url field (resolved upstream URL) — the skill does not instruct automatically fetching that URL, but users/agents should be cautious if they navigate to or fetch those upstream links.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is downloaded or written by the skill itself — risk from install mechanism is minimal.

Credentials

No environment variables or credentials are required. The declared dependencies (pilotctl binary, daemon on network 9, pilot-protocol/pilot-service-agents skills) are proportional to querying an overlay of service agents.

Persistence & Privilege

always is false and the skill does not request permanent presence or modifications to other skills. Normal autonomous invocation is allowed (platform default) but not an additional privilege specific to this skill.

Assessment

This skill appears to be what it says: a thin wrapper of instructions to query Pilot Protocol service agents. Before installing, ensure you trust the pilotctl binary and the Pilot Protocol daemon you will join to network 9 (running a daemon on an overlay gives network access to other peers). Be cautious about any upstream_url values returned by agents — they may point to external resources you or an agent could fetch. Verify the provenance of the pilot-protocol and pilot-service-agents skills and only run pilotctl from a trusted release; if you are uncomfortable with autonomous agents interacting with an overlay network, keep model invocation disabled or restrict usage to manual runs.

Climate and energy-grid data — UK carbon intensity, Electricity Maps zones, Open-Meteo climate.

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
carbon-intensity-regional	Carbon Intensity Regional
electricity-maps-zones	Electricity Maps CO2 grid zone catalog
open-meteo-climate	Climate change projections (CMIP6 models)
uk-carbon-intensity	GB electricity grid carbon intensity (live)

What you can expect

• Carbon-intensity feeds at 30-minute resolution
• Electricity-zone metadata and current mix

What NOT to expect

• Guaranteed global coverage — regional feeds vary
• Scenario modelling — only actual observations

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

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

# 3. Query it
pilotctl --json send-message carbon-intensity-regional --data '/data {"region":"1"}'
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.