Pilot Service Agents Nature

v1.0.0

Biodiversity observations — iNaturalist species sightings. Use this skill when: 1. Looking up recent species observations near a location Do NOT use this ski...

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-nature.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-service-agents-nature
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (iNaturalist-style observations) match the requested artifacts: only the pilotctl binary, the pilot-protocol daemon, and access to the network/agents are required. Nothing requested appears unrelated to retrieving observation data.
Instruction Scope
SKILL.md only instructs the agent to use pilotctl to discover agents, read agent contracts (/help), request structured data (/data) and human summaries (/summary). It does not ask for arbitrary file reads, environment variables, or transmitting unrelated system data.
Install Mechanism
No install spec is present (instruction-only), so nothing new will be written to disk by the skill itself. The risk surface is limited to the external pilotctl binary and daemon which the user must already install/run.
Credentials
The skill declares no environment variables, credentials, or config paths. That is proportional to its function of querying overlay agents.
Persistence & Privilege
always:false and normal autonomous invocation are used. The skill does not request persistent privileges or modify other skills/configs; its runtime behavior is limited to calling pilotctl and reading the pilotctl inbox.
Assessment
This skill is coherent and limited: it only instructs use of the pilotctl tool to query agents on the Pilot Protocol network. Before installing, verify you obtain pilotctl from a trusted source and understand that joining the protocol network (network 9) connects your daemon to an overlay of peers — agent responses may include upstream URLs or external links, so avoid sending secrets or sensitive data to agents. If you don't already run pilotctl/daemon, review the Pilot Protocol project's documentation and binaries to ensure they are legitimate and appropriate for your environment.

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

Runtime requirements

Binspilotctl
latestvk974v1nqx6c7thk6v1y17y6trx85qhvt
37downloads
0stars
1versions
Updated 19h ago
v1.0.0
MIT-0

pilot-service-agents-nature

Biodiversity observations — iNaturalist species sightings.

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
inaturalist-obsiNaturalist species observations - biodiversity research

What you can expect

  • Citizen-science observation records with photos and place names

What NOT to expect

  • Taxonomic authority records — this is observation data, not a taxonomy

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

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

# 3. Query it
pilotctl --json send-message inaturalist-obs --data '/data {"taxon_name":"Panthera tigris","per_page":3}'
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...