Skill: teoslayer/pilot-service-agents-nature (version 1.0.0)

--- name: pilot-service-agents-nature description: > Biodiversity observations — iNaturalist species sightings. Use this skill when: 1. Looking up recent species observations near a location Do NOT use this skill when: - Pet / domestic animal info - Protected-species enforcement data tags: - pilot-protocol - service-agents - nature - biodiversity license: AGPL-3.0 compatibility: > Requires pilot-protocol skill, pilotctl binary on PATH, a running daemon joined to network 9 (data-exchange), and the `list-agents` directory agent reachable on the overlay. metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # 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) | Hostname | Description | |---|---| | `inaturalist-obs` | iNaturalist 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) ```bash # 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: ```json { "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 ```bash # 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.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)