local-places

Query a local Google Places proxy to locate businesses and points of interest.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill local-places-balic-ai-ml-r-d-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-places
Source: https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents/tree/main/packages/skills/skills/local-places
Command: npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill local-places-balic-ai-ml-r-d-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate local businesses and points of interest by querying a local Google Places proxy, enabling quick turnarounds for location-based queries and reducing dependency on external endpoints during agent conversations.

Core Features & Use Cases

  • Resolve vague locations to a concrete area, then search for nearby places with a simple natural-language query.
  • Apply precise filters such as type (one type max), open-now status, minimum rating, and price level to tailor results.
  • Return structured results including place_id, name, address, location, rating, price level, types, hours, and optional contact details for quick ingestion into downstream tasks.

Quick Start

Start the server locally, resolve a location, and perform a place search with a simple query.

Frequently Asked Questions about local-places

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

FAQPage Schema
How do I find nearby places using a local Google Places proxy?

To find nearby places, query the local Google Places proxy by first resolving a vague location to a concrete area, then executing a filtered search for points of interest to return structured results.

What filters can I apply when searching for local businesses with Google Places?

When searching for local businesses, you can apply precise filters including business type (one type max), open-now status, minimum rating, and price level to tailor the structured results returned.

Do I need a Google Places API key to resolve vague locations locally?

Yes, resolving vague locations locally requires a running local proxy and a valid GOOGLE_PLACES_API_KEY to process queries and handle validation, paging, and error reporting.

How does a local API proxy handle Google Places search errors and paging?

A local API proxy handles Google Places search errors and paging by validating requests, managing result pagination, and reporting errors directly within the agent conversation workflow.

What data does a local Google Places search return for downstream tasks?

A local Google Places search returns structured data including place_id, name, address, location, rating, price level, types, hours, and optional contact details for quick ingestion into downstream tasks.

Why use a local proxy for Google Places instead of direct external endpoints?

Using a local proxy for Google Places enables quick turnarounds for location-based queries and reduces dependency on external endpoints during agent conversations.