biodiversity corridor calculator

v1.0.0

Calculates biodiversity corridor connectivity and ecological value for clusters of H3 hexagonal land parcels using landscape ecology models.

0· 616·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for nikhilp1234567/biodiversity-corridor-calculator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "biodiversity corridor calculator" (nikhilp1234567/biodiversity-corridor-calculator) from ClawHub.
Skill page: https://clawhub.ai/nikhilp1234567/biodiversity-corridor-calculator
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
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 biodiversity-corridor-calculator

ClawHub CLI

Package manager switcher

npx clawhub@latest install biodiversity-corridor-calculator
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description align with the runtime instructions: the SKILL.md tells the agent to POST H3 indices and a center coordinate to an API that claims to perform connectivity and ecological-value analysis. The skill does not request unrelated credentials or binaries. However, there is no source repository or project homepage and the API host (https://www.nikhilp.online) is undocumented — lack of provenance is noteworthy even though the technical capability is consistent with the stated purpose.
!
Instruction Scope
The instructions are narrowly scoped to calling a single external API endpoint (POST /api/analyze) with H3 indices and center coordinates. They do not instruct the agent to read local files or access unrelated environment variables. The main concern is that the skill directs potentially sensitive geolocation data (projectHexes, centerLat/centerLng) to an external, unknown third‑party server; that is a privacy/trust risk even though it is functionally coherent.
Install Mechanism
There is no install spec and no code files — instruction-only. This is low risk in terms of local code execution or disk writes.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate to an instruction-only skill that simply calls a public API. The lack of authentication could mean the API is public or expects no secrets — which is consistent but also means calls are unauthenticated and rate-limited as noted.
Persistence & Privilege
always is false and the skill does not request system-wide modifications or persistent privileges. The skill can be invoked autonomously by the agent (default), which is normal; consider limiting autonomous invocation if you don't want the agent sending data to the external API without prompting.
What to consider before installing
This skill appears to do what it says (send H3 indices to an analysis API), but exercise caution before enabling it: 1) Provenance: there is no source repo or homepage — verify the API owner/trustworthiness (https://www.nikhilp.online) before sending real project data. 2) Data sensitivity: the skill will transmit geolocation/H3 indices and center coordinates to a third party; do not send confidential or sensitive locations unless you trust the operator and their data handling policy. 3) Test safely: try with synthetic or public data first and confirm responses and rate‑limit behavior. 4) If you need stronger guarantees, prefer a skill backed by a known organization or a local/offline implementation, or require an authenticated API on infrastructure you control. 5) If you allow autonomous invocation, limit the agent's scope so it cannot repeatedly send location data without explicit user approval.

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

latestvk97crj6wjctj420ttz4xf0h2pn81a6ec
616downloads
0stars
1versions
Updated 2mo ago
v1.0.0
MIT-0

Open Claw Agent Skill: Biodiversity Corridor Analyst Description This skill allows an autonomous agent to analyze and value biodiversity corridors using advanced landscape ecology models. It processes H3 geospatial indices to calculate connectivity scores, visualize landscape resistance, and assess ecological premium values for conservation projects.

The agent can use this skill to:

  1. Analyze Connectivity: Evaluate a set of hexagonal land parcels (H3 indices) to determine their potential as biodiversity corridors, stepping stones, or regeneration zones.
  2. Assess Landscape Context: Retrieve data on surrounding land cover and ecological resistance to understand the broader environmental context of a project site.

Server Configuration Base URL: https://www.nikhilp.online/biodiversity-corridor-calculator API Base Path: /api


  1. Analyze Connectivity Endpoint: POST https://www.nikhilp.online/biodiversity-corridor-calculator/api/analyze

Description Analyzes the connectivity and ecological potential of a specified cluster of H3 hexagons. The analysis considers local habitat quality and regional landscape structure to classify the area into scenarios like "Vital Corridor," "Habitat Expansion," or "Stepping Stone."

Input Schema (JSON) centerLat (Number): The latitude of the center point for the analysis region (between -90 and 90).

centerLng (Number): The longitude of the center point for the analysis region (between -180 and 180).

projectHexes (Array of Strings): A list of H3 hexagonal indices (resolution 9 is standard) representing the land parcels to be analyzed. Maximum 50 hexes per request to ensure performance.

Usage Example To analyze a small cluster of land parcels in a specific region:

JSON { "centerLat": 51.5074, "centerLng": -0.1278, "projectHexes": [ "892a100d2b3ffff", "892a100d2b7ffff", "892a100d2bbffff" ] }

Response Format JSON { "results": [ { "h3Index": "892a100d2b3ffff", "originalCode": 10, "natureState": 1, "scenario": { "code": "CORRIDOR", "label": "Vital Corridor", "description": "This area acts as a bridge...", "color": "#f59e0b", "priority": 1.0 }, "resistance": 1, "localNature": 0.45, "landscapeNature": 0.30 } ], "context": [ { "h3Index": "892a100d28fffff", "originalCode": 50 } ... ] }

Notes

  • Rate Limiting: The API is strictly rate-limited (approx. 5 requests per minute). Ensure you can handle 429 Too Many Requests responses gracefully by waiting before retrying.
  • H3 Indices: The system relies on H3 geospatial indexing. Ensure you can generate or work with valid resolution 9 H3 strings.

Comments

Loading comments...