Camino Places.Bak

Locate places using flexible query formats - free-form search or structured address components. Returns coordinates, addresses, and optional street-level pho...

Security Scan

The skill is generally coherent with a geocoding/place-lookup capability and only requests a single API key, but there are small inconsistencies (missing declared binaries, metadata mismatch, and install instructions that pull code from GitHub) that warrant review before installation.

Purpose & Capability

Name/description match the behavior: the script and SKILL.md call Camino's API (api.getcamino.ai/search) and only require an API key for that service. The SKILL.md clarifies /places vs /search differences. This purpose aligns with requested CAMINO_API_KEY and the requests the skill makes.

Instruction Scope

Runtime instructions are limited to sending the user-provided JSON to the Camino API and returning results. The SKILL.md tells users to store the API key in ~/.claude/settings.json (which is persistent) and to use npx to install companion skills from a GitHub repo — both of which expand scope beyond just running the included script. The script itself does not read or exfiltrate other local files or environment variables.

Install Mechanism

There is no formal install spec in the manifest (instruction-only skill), but the README suggests installing via npx from a GitHub repo (https://github.com/barneyjm/camino-skills). Pulling code via npx/github is common but means you should inspect the repository before running. The packaged files include a harmless-looking shell script; no high-risk remote download URLs are embedded in the files themselves.

Credentials

The skill legitimately needs a single CAMINO_API_KEY — that's proportionate. However, the registry metadata at the top lists no required binaries while SKILL.md and scripts require curl and jq; this mismatch between declared requirements and actual runtime checks is an incoherence that should be resolved before trusting the skill (the script will fail or behave unexpectedly if those binaries are missing).

Persistence & Privilege

The skill does not request elevated privileges or always:true. It suggests adding the API key to ~/.claude/settings.json (local persistent storage of the key), which is normal for credentials but worth noting because it persists the secret on disk.

What to consider before installing

This skill appears to do what it says (geocoding/place lookup) and only needs a Camino API key, but take these precautions before installing: - Inspect the GitHub repo referenced by the install instructions (npx skills add https://github.com/barneyjm/camino-skills) before running any installer. - Ensure curl and jq are available (the script checks for them) or update the manifest to reflect those requirements — the current registry metadata omits them. - Prefer using a scoped API key with minimal permissions and consider not storing it in a shared/global settings file if you are concerned about persistence; use a local or per-project mechanism if possible. - Note the small metadata inconsistencies (ownerId in _meta.json differs from registry owner and declared binaries mismatch); ask the publisher to clarify those before trusting the package. - If you will run the included script, review scripts/places.sh to confirm it only sends the JSON you provide to https://api.getcamino.ai/search; avoid passing sensitive secrets in the JSON payload.

Installation

Companion Skills: This is part of the Camino AI location intelligence suite. Install all available skills (query, places, relationship, context, route, journey, real-estate, hotel-finder, ev-charger, school-finder, parking-finder, fitness-finder, safety-checker, travel-planner) for comprehensive coverage.

# Install all skills from repo
npx skills add https://github.com/barneyjm/camino-skills

# Or install specific skills
npx skills add https://github.com/barneyjm/camino-skills --skill places

Via clawhub:

npx clawhub@latest install places
# or: pnpm dlx clawhub@latest install places
# or: bunx clawhub@latest install places

Places - Flexible Place Lookup

Locate places using free-form queries or structured address components. Supports geocoding, place lookup, and optional street-level imagery.

Places vs Query

Feature	/places	/query
Method	POST	GET
Input	Free-form OR structured address	Natural language with context
Coordinates	Returns them (geocoding)	Can auto-generate for search center
AI Ranking	No	Yes
Photos	Optional street-level imagery	No
Best For	"Eiffel Tower", address lookup	"quiet cafes near Times Square"

Use /places for geocoding addresses or finding specific named places. Use /query for natural language queries with AI ranking.

Setup

Instant Trial (no signup required): Get a temporary API key with 25 calls:

curl -s -X POST -H "Content-Type: application/json" \
  -d '{"email": "[e-mail]"}' \
  https://api.getcamino.ai/trial/start

Returns: {"api_key": "camino-xxx...", "calls_remaining": 25, ...}

For 1,000 free calls/month, sign up at https://app.getcamino.ai/skills/activate.

Add your key to Claude Code:

Add to your ~/.claude/settings.json:

{
  "env": {
    "CAMINO_API_KEY": "your-api-key-here"
  }
}

Restart Claude Code.

Usage

Via Shell Script

# Free-form search for a landmark
./scripts/places.sh '{"query": "Eiffel Tower"}'

# Search with street-level photos
./scripts/places.sh '{"query": "Empire State Building", "include_photos": true}'

# Structured address search
./scripts/places.sh '{"street": "1600 Pennsylvania Avenue", "city": "Washington", "state": "DC", "country": "USA"}'

# Search by city
./scripts/places.sh '{"city": "San Francisco", "state": "California", "limit": 5}'

Via curl (direct API calls)

The skill is named places but calls the /search API endpoint. For direct API calls:

curl -X POST -H "X-API-Key: $CAMINO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "Eiffel Tower", "include_photos": true}' \
  "https://api.getcamino.ai/search"

Parameters

Parameter	Type	Required	Default	Description
query	string	No*	-	Free-form search (e.g., "Eiffel Tower", "Central Park")
amenity	string	No	-	Amenity/POI type
street	string	No	-	Street name and number
city	string	No	-	City name
county	string	No	-	County name
state	string	No	-	State or province
country	string	No	-	Country name or code
postalcode	string	No	-	Postal/ZIP code
limit	int	No	10	Maximum results (1-50)
include_photos	bool	No	false	Include street-level imagery
photo_radius	int	No	100	Photo search radius in meters (10-500)
mode	string	No	"basic"	"basic" or "advanced" search depth

*Either query or at least one address component is required.

Response Format

[
  {
    "display_name": "Eiffel Tower, 5 Avenue Anatole France, 75007 Paris, France",
    "lat": 48.8584,
    "lon": 2.2945,
    "type": "tourism",
    "importance": 0.95,
    "address": {
      "tourism": "Eiffel Tower",
      "road": "Avenue Anatole France",
      "city": "Paris",
      "country": "France",
      "postcode": "75007"
    },
    "photos": [
      {
        "url": "https://...",
        "lat": 48.8580,
        "lon": 2.2948,
        "heading": 45
      }
    ],
    "has_street_imagery": true
  }
]

Examples

Geocode an address

./scripts/places.sh '{"street": "350 Fifth Avenue", "city": "New York", "state": "NY"}'

Find a landmark with photos

./scripts/places.sh '{"query": "Statue of Liberty", "include_photos": true, "photo_radius": 200}'

Search by postal code

./scripts/places.sh '{"postalcode": "90210", "country": "USA"}'

Advanced mode for richer data

./scripts/places.sh '{"query": "Times Square", "mode": "advanced", "include_photos": true}'

Best Practices

• Use query for landmarks, POIs, and well-known places
• Use structured address fields for precise geocoding
• Enable include_photos when you need visual context
• Use mode: "advanced" for web-enriched place data
• Combine address components for more accurate results