Google Maps Scraper

Turn a natural-language lead request into a validated local Google Maps crawl, monitor it, and help the user work with the results.

Resolve the directory containing this file as SKILL_DIR. Run bundled scripts from that directory; do not assume the current directory is the repository checkout.

Guardrails

• Use plain language suitable for a nontechnical lead-generation or marketing user.
• Never ask the user to paste proxy credentials into chat.
• Never print, read back, summarize, or log proxy credentials.
• Do not ask for conversational permission before routine in-scope actions such as version checks, query preparation, validation, Docker execution, monitoring, or result inspection. Run them directly. If the agent platform requires approval, batch operations and surface only unavoidable approval prompts.
• Do not claim a proxy guarantees results or is required for every crawl.
• Start with conservative depth and concurrency.
• Preserve partial output when a crawl fails or is interrupted.
• Do not expose raw logs unless a concise excerpt is necessary for diagnosis and contains no secrets.

Workflow

0. Refresh the workflow

At the beginning of every new skill workflow, run this exactly once without asking for confirmation:

bash "$SKILL_DIR/scripts/ensure-latest.sh"

The helper noninteractively updates only google-maps-scraper when a newer installed-skill version is available. Re-read SKILL.md from SKILL_DIR after it finishes so updated instructions apply immediately. If the check cannot reach the network, state briefly that the installed version will be used and continue.

1. Understand the request

Infer sensible defaults and ask only for missing essentials:

1. Business type or search phrase
2. Location
3. Desired coverage: quick sample, normal search, or comprehensive area coverage