local-places

Query a local Google Places API proxy for place searches and location resolution.

2|1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/zhangziliang04/moltbot_deepseek --skill local-places-zhangziliang04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-places
Source: https://github.com/zhangziliang04/moltbot_deepseek/tree/main/skills/local-places
Command: npx skills add https://github.com/zhangziliang04/moltbot_deepseek --skill local-places-zhangziliang04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables fast discovery of places by querying a local Google Places API proxy, turning free-text questions into actionable results without relying on external network calls to Google directly.

Core Features & Use Cases

  • Search nearby places by text query with optional location bias and simple filters (types, open_now, min_rating, price_levels).
  • Resolve a user-provided location into a usable coordinates context for subsequent searches.
  • Retrieve detailed information for a selected place via its place_id.

Quick Start

Run the local API server and perform a resolve followed by a search to discover nearby places.

Frequently Asked Questions about local-places

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search nearby places using a Google Places API proxy?

To search nearby places, send a free-text query to the /places/search endpoint with optional location bias. The Google Places API proxy returns structured place results without direct external network calls to Google.

Can I filter Google Places search results by rating, price, and open status?

You can filter Google Places search results using basic filters for types, open_now, min_rating, and price_levels. These filters are applied directly within the /places/search endpoint request.

How do I resolve a location into coordinates for a places search?

Resolve a user-provided location into usable coordinates by querying the /locations/resolve endpoint. The resolved coordinates provide the location bias context needed for subsequent nearby places searches.

How do I retrieve detailed information for a specific place_id?

Retrieve detailed information for a specific place by calling the /places/{place_id} endpoint. This fetches structured response data for the selected place directly through the local Google Places proxy.

Does FastAPI work well for building a local Google Places proxy server?

FastAPI is used to build this local Google Places proxy server, exposing typed requests and structured responses. It supports the /places/search, /places/{place_id}, and /locations/resolve endpoints within a local server context.

What are the limitations of using a local proxy for location resolving?

The local proxy operates within a local server context and relies on a Google Places API proxy rather than direct external network calls. Location resolving is limited to providing basic coordinates context for subsequent searches.