Plan complete day trips, walking tours, and multi-stop itineraries with time budgets using Camino AI's journey planning and route optimization.
Security Analysis
high confidenceThe skill's requirements, runtime instructions, and included script are consistent with a travel-planning wrapper around the Camino AI journey endpoint and do not request unrelated credentials or risky install behavior.
Name/description (travel planning) matches what the skill does: it posts user-provided waypoint JSON to Camino's /journey endpoint. The only required credential is CAMINO_API_KEY, which is appropriate for that API. Declared binaries (curl, jq) are used by the included script.
SKILL.md and the shell script only validate JSON, require at least two waypoints, and send the JSON to https://api.getcamino.ai/journey. Instructions to obtain a trial key and to add CAMINO_API_KEY to ~/.claude/settings.json are within scope. There are no instructions to read unrelated files, access other env vars, or transmit data to unexpected endpoints.
This is instruction-only with a small included shell script; there is no automatic download-from-URL or opaque binary install in the skill itself. SKILL.md suggests using npx to add a GitHub-hosted skills repo (user-run action) — advise reviewing that repo before running, but the skill's own files are simple and transparent.
Only CAMINO_API_KEY is required and is the declared primary credential. No other secrets, unrelated credentials, or config paths are requested. The script uses that key only to call the Camino API.
Skill is not always-enabled and does not request elevated or persistent system privileges. It does not modify other skills or system-wide configs beyond the guidance to add the API key to the user's Claude settings (a normal per-user config step).
Guidance
This skill appears coherent and minimal: it sends your waypoint JSON and your CAMINO_API_KEY to https://api.getcamino.ai/journey. Before installing or running: (1) obtain your API key from the official Camino site and treat it like any API secret (don’t paste it into untrusted places); (2) review the GitHub repo referenced by the install commands before running npx to ensure you trust its source; (3) if you want tighter safety, create a Camino key with minimal scope or a usage-limited/trial key; (4) verify that curl and jq are up-to-date on your machine. If you see any unexpected network endpoints or additional required env vars in future versions, stop and re-check the files.
Latest Release
v0.2.0
- Added curl and jq as required binaries in the skill metadata. - No other user-visible changes.
Popular Skills
Published by @James-southendsolutions on ClawHub