Route between two locations

Name and description match the code and instructions: the script builds a query from start/end coordinates and calls https://api.getcamino.ai/route. The only required credential is CAMINO_API_KEY, which is appropriate for this purpose. Note: the registry metadata listed no required binaries, but SKILL.md and the script require curl and jq — this is a minor metadata inconsistency.

SKILL.md and scripts stay within scope: they validate JSON, require start/end coords, read CAMINO_API_KEY, and make an HTTPS GET to the Camino API. No instructions to read other files, harvest unrelated env vars, or POST data to third-party endpoints are present. The doc does advise adding the API key to ~/.claude/settings.json and offers a trial endpoint (https://api.getcamino.ai/trial/start), both of which are reasonable for this integration.

There is no formal install spec (instruction-only), and the included scripts are simple and static. However, the README suggests installing an entire GitHub repo via npx (npx skills add https://github.com/barneyjm/camino-skills), which will pull remote code — review that repository before running the installer. The provided local script does not download or execute remote code itself.

The skill only requests one credential (CAMINO_API_KEY) and uses it directly in API calls. No extra tokens, keys, or unrelated environment variables are requested. This is proportionate to a routing API integration. (Again: SKILL.md expects curl/jq even though registry metadata omitted them.)

The skill does not request always:true or attempt to modify other skills or system settings. It runs on demand and only requires the user-provided API key to operate.