goplacesQuery Google Places for text search, place details, resolve, reviews, or scriptable JSON via goplaces.
Install via ClawdBot CLI:
clawdbot install steipete/goplacesInstall goplaces (brew):
brew install steipete/tap/goplacesRequires:
Grade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/steipete/goplacesAudited Apr 16, 2026 · audit v1.0
Generated Feb 16, 2026
Travelers can use goplaces to find highly-rated coffee shops or restaurants open now near their location, filtering by rating and price level. This helps them quickly discover quality dining options without extensive research, enhancing their travel experience.
Real estate agents can search for amenities like grocery stores or parks within a specific radius of a property using location bias parameters. This provides data to highlight neighborhood features in listings, supporting property valuation and marketing efforts.
Event planners can query details for potential venues, including reviews and price levels, to assess suitability for conferences or gatherings. The JSON output allows integration into custom tools for comparing options and managing logistics efficiently.
Food delivery services can use the search function with pagination to batch-process restaurant data in specific areas, such as fetching all pizza places in a city. This aids in expanding service coverage and optimizing delivery routes based on place availability.
Developers can integrate goplaces into mobile apps to provide tourists with real-time place searches and details, using the resolve feature for ambiguous location queries. This enhances app functionality by offering accurate, human-friendly place information on-the-go.
Offer a subscription-based service that integrates goplaces into existing business software, such as CRM or marketing tools, for automated place data enrichment. Revenue is generated through monthly fees based on API usage tiers and support levels.
Provide consulting services to businesses leveraging goplaces for market research, analyzing place trends and competitor locations using JSON output. Revenue comes from project-based contracts and ongoing analysis reports tailored to client needs.
Develop and license custom travel or navigation apps that use goplaces as the backend for place searches, targeting travel agencies or hospitality companies. Revenue is generated through licensing fees and revenue-sharing agreements based on app usage.
💬 Integration Tip
Set the GOOGLE_PLACES_API_KEY environment variable securely and use the --json flag for script automation to parse output easily.
Scored Apr 19, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.
Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).