Goplaces
Query Google Places for search, resolve, details, and reviews from the terminal or agent-driven scripts.
Overview
goplaces is an agent skill for the Build phase that queries Google Places for text search, resolve, place details, reviews, and scriptable JSON via the goplaces CLI.
Install
npx skills add https://github.com/steipete/clawdis --skill goplacesWhat is this skill?
- Modern Google Places API (New) CLI with search, resolve, details, and reviews
- Geo bias (--lat/--lng/--radius-m), open-now, min-rating, pagination via --page-token
- Human-readable default output plus --json for automation
- Homebrew install path and GOOGLE_PLACES_API_KEY as primaryEnv
- Price levels 0..4 (free to very expensive)
- Type filter sends only the first --type value per API constraint
Adoption & trust: 1.9k installs on skills.sh; 378k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Google Places search and details in a terminal or agent workflow without writing and maintaining a Places API client.
Who is it for?
Indie builders adding local search, resolve, or review enrichment to CLIs and coding agents with a Places API key.
Skip if: Products that cannot use Google Places billing, or teams that only need in-app mobile SDK maps with no server/CLI layer.
When should I use this skill?
Query Google Places for text search, place details, resolve, reviews, or scriptable JSON via goplaces
What do I get? / Deliverables
You run goplaces commands (or agent-guided equivalents) and get place lists, resolved locations, or detail/review payloads in text or JSON.
- Place search results
- Resolved place candidates
- Place details and optional review JSON
Recommended Skills
Journey fit
How it compares
CLI integration skill for Places API (New), not an MCP server or embedded map widget.
Common Questions / FAQ
Who is goplaces for?
Solo developers and agent users who want scriptable Google Places search, resolve, and details from the shell with minimal custom code.
When should I use goplaces?
During Build while wiring location features, debugging place IDs, or piping --json results into backend scripts and agent tools.
Is goplaces safe to install?
Check this page’s Security Audits panel and treat GOOGLE_PLACES_API_KEY as a secret; review the steipete/clawdis repo before installing the Homebrew binary.
SKILL.md
READMESKILL.md - Goplaces
# goplaces Modern Google Places API (New) CLI. Human output by default, `--json` for scripts. Install - Homebrew: `brew install steipete/tap/goplaces` Config - `GOOGLE_PLACES_API_KEY` required. - Optional: `GOOGLE_PLACES_BASE_URL` for testing/proxying. Common commands - Search: `goplaces search "coffee" --open-now --min-rating 4 --limit 5` - Bias: `goplaces search "pizza" --lat 40.8 --lng -73.9 --radius-m 3000` - Pagination: `goplaces search "pizza" --page-token "NEXT_PAGE_TOKEN"` - Resolve: `goplaces resolve "Soho, London" --limit 5` - Details: `goplaces details <place_id> --reviews` - JSON: `goplaces search "sushi" --json` Notes - `--no-color` or `NO_COLOR` disables ANSI color. - Price levels: 0..4 (free -> very expensive). - Type filter sends only the first `--type` value (API accepts one).