local-placesSearch for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Install via ClawdBot CLI:
clawdbot install steipete/local-placesRequires:
Grade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → http://127.0.0.1:8000/locations/resolveCalls external URL not in known-safe list
https://github.com/Hyaxia/local_placesUses known external API (expected, informational)
googleapis.comAI Analysis
The skill's primary operation is a local proxy to the Google Places API, which is a legitimate and documented external service. The 'UNKNOWN_DATA_SINK' signal is a false positive, as the endpoint (127.0.0.1:8000) is the user's own local server, not an external exfiltration point. The main risk is the dependency on a third-party API key, but the skill's behavior aligns with its stated purpose.
Generated Mar 1, 2026
Travelers in a new city can use the skill to find nearby restaurants, cafes, or attractions based on real-time location and preferences like open status and ratings. It helps them quickly identify top-rated dining options without extensive manual searching, enhancing their travel experience.
Event planners can search for venues such as restaurants, gyms, or cafes by specifying location, price level, and ratings to find suitable spots for meetings or gatherings. The two-step location resolution ensures accurate targeting in specific neighborhoods or cities.
Real estate agents can use the skill to analyze amenities near properties, such as nearby cafes, gyms, or restaurants, to provide clients with insights into local lifestyle options. Filters like open now and min rating help highlight quality establishments.
Food delivery platforms can integrate the skill to dynamically suggest pickup or drop-off locations based on user queries and location bias, improving route efficiency and customer satisfaction by prioritizing open, highly-rated restaurants.
Companies planning office moves can search for nearby amenities like cafes and gyms to assess neighborhood suitability for employees. The skill's filters allow them to evaluate options based on ratings and price levels to support decision-making.
Offer the Google Places API proxy as a paid subscription for developers or businesses needing local search capabilities without managing API keys directly. Revenue comes from tiered plans based on request volume and advanced features like priority support.
License the skill as a white-label solution for mobile apps or websites in industries like travel or real estate, allowing them to embed local search functionality. Revenue is generated through one-time licensing fees or revenue-sharing agreements.
Provide basic search and resolve features for free, with premium features such as higher limits, advanced filters, or detailed analytics available for a fee. This model attracts users initially and monetizes through upgrades.
💬 Integration Tip
Ensure the GOOGLE_PLACES_API_KEY is securely stored in environment variables and test the two-step flow with location resolution before full deployment to handle vague user inputs effectively.
Scored Apr 19, 2026
Audited Apr 16, 2026 · audit v1.0
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).