agentleFS
skills-agents-coskills-agents-co/skills-and-agents-library/local-lead-prospector/SKILL.md

local-lead-prospector

Skill1 starsChanged 32 days agoMITView on GitHub

Assembles an outreach list of local businesses for an SDR from an industry + region pair. Returns a CSV with name, category, address, phone, website, rating, review count, and a Google Maps source URL, plus a markdown summary. Listing data only. No decision-maker names, no personal emails, no LinkedIn scraping. Google Places API (New) is the preferred path and requires GOOGLE_MAPS_API_KEY. A Playwright + Chromium scrape of public Google Maps results exists as an opt-in fallback, gated behind an explicit confirmation, because scraping Google Maps is against Google's Terms of Service. Use this skill when an SDR asks to "find me dentists in Austin", "build a lead list for HVAC companies in Denver", "I need contacts for law firms in Chicago", "give me a prospecting list", or "who should I cold-call in this market". Do NOT trigger on single-consumer lookups like "find me a good dentist near me", "what is the best taco place in Austin", or "where should I take a client to dinner in SoHo". Those are one-shot recommendations, not lead lists.

  • Reads credentials
  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default is 40 rows. Ask only if the user has not stated a number.

    line 46
  2. Very specific:

    If GOOGLE_MAPS_API_KEY is set, use the API.

    line 50
  3. Very specific:

    If the env var is missing, explain that the API is preferred, point at references/places_api_setup.md, and offer the scrape fallback.

    line 51
  4. Distinctive:

    After the run, post this exact structure back to the user:

    line 92
  5. Distinctive:

    Over-broad region: If the user is asking for a state or a country, do not run.

    line 125
  6. Distinctive:

    Over-volume: If the user asks for more than 100, do not run.

    line 126
  7. Distinctive:

    Do not run the scrape against Google Maps in CI or on a shared IP without understanding that it violates Google's Terms of Service.

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Local Lead Prospector

Compliance up front

Google Maps listing data is the source. Two paths exist and they are not equal.

  • Preferred path: Google Places API (New). Official, paid, billed per request. Requires GOOGLE_MAPS_API_KEY in the environment. Free tier is small, so a cost estimate is shown before any pull above 50 rows.
  • Fallback path: Playwright scrape of Google Maps. This is against Google's Terms of Service. It exists for cases where the user has no API key and accepts the risk. It only runs after the user explicitly confirms in the same turn. Do not run it silently.

Listing data only. Never produce decision-maker names, personal emails, or LinkedIn profiles. Enrichment past the public Google Maps listing is out of scope.

What you get per business

Each row in the CSV:

  • name
  • category (primary type from Google)
  • address
  • phone (international format when Google has it, blank when missing)
  • website (blank when missing)
  • rating (0.0 to 5.0)
  • reviews (count)
  • source_url (Google Maps URL for this place)

Missing phone or website cells stay blank. Do not fabricate or guess values.

Workflow

1. Confirm industry and region

Both must be specific. If either is vague, ask one clarifying question and stop.

  • "Texas" is too broad. Ask for a city or metro.
  • "small business" is too broad. Ask for an industry like "dentists", "HVAC", "law firms".
  • "Austin, TX" is real.
  • "dentists in Austin, TX" is ready to run.

2. Confirm count

Default is 40 rows. Ask only if the user has not stated a number. If the user asks for more than 100, push back and suggest splitting by sub-region (zip, neighborhood, adjacent city). Over 100 in one pull tends to hit the same dense cluster and waste cost.

3. Pick the method

  • If GOOGLE_MAPS_API_KEY is set, use the API. No prompt, no scrape.
  • If the env var is missing, explain that the API is preferred, point at references/places_api_setup.md, and offer the scrape fallback. Do not run the scrape without explicit confirmation from the user in this turn.

4. Cost estimate before large pulls

If the requested count is above 50 and the API path is being used, surface the cost estimate first. Pricing tier is Places API (New) Text Search. At the time of writing, Text Search is billed per request and each request returns up to 20 results, so a 100-row pull is about 5 paginated requests. Show the estimate and ask the user to confirm before running.

5. Run the script

API path:

python scripts/fetch_places_api.py \
  --industry "dentists" \
  --region "Austin, TX" \
  --count 40 \
  --out leads.csv

Scrape path (only after user confirms):

python scripts/scrape_listings.py \
  --industry "dentists" \
  --region "Austin, TX" \
  --count 40 \
  --out leads.csv \
  --yes-tos

6. Write the CSV and the summary

Both scripts emit the same CSV schema. Header line is byte-identical:

name,category,address,phone,website,rating,reviews,source_url

Then post the markdown summary in the chat (template below).

Summary template

After the run, post this exact structure back to the user:

## Lead list: <industry> in <region>

- Total leads: <N>
- With phone: <P> (<P/N>%)
- With website: <W> (<W/N>%)
- Source: Google Places API (New) | Google Maps scrape (ToS opt-in)
- CSV: <path to leads.csv>

### Sample (first 10)

| Name | Category | Phone | Website | Rating | Reviews |
|---|---|---|---|---|---|
| ... | ... | ... | ... | ... | ... |

### SDR notes

- Rows without a phone are usable for email-only sequences.
- Rows without a website are local, likely solo operators. Cold-call first.
- Ratings below 3.5 with high review counts often signal an operations gap, which is a real opening for a pitch about ops tooling.
- The CSV does not contain decision-maker names. Pair with manual LinkedIn lookups before sending personalized outreach.

Numbers are derived directly from the CSV that was written. Sample table is the first 10 rows. If fewer than 10 rows came back, show them all.

Failure handling

Surface clear messages. Never dump a Python traceback at the user.

  • Zero rows. Exit cleanly. Tell the user the query returned nothing and suggest a broader industry term or a wider region. No traceback.
  • Consent page (scrape only). The fallback dismisses Google's consent interstitial. If it cannot, it exits with "Google consent page blocked the scrape" and suggests trying the API path.
  • Over-broad region. If the user is asking for a state or a country, do not run. Ask for a city or metro.
  • Over-volume. If the user asks for more than 100, do not run. Suggest splitting by sub-region.
  • API quota exceeded. Surface as "Google Places API quota exceeded for the current period. Either wait for reset or raise the quota in Google Cloud Console."
  • API billing not enabled. HTTP 403 with "billing" in the body. Surface as "Google Places API billing is not enabled on this Cloud project. See references/places_api_setup.md."
  • API key invalid. API_KEY_INVALID in the response. Surface as "GOOGLE_MAPS_API_KEY is invalid or restricted. Check the key in Google Cloud Console."

Dedupe

  • API path dedupes on place_id across paginated pageToken responses.
  • Scrape path dedupes on a name + address key across scroll batches.

Out of scope

  • Decision-maker enrichment (no names, no titles).
  • Personal email lookup.
  • LinkedIn scraping.
  • Paid enrichment APIs (Apollo, ZoomInfo, Clearbit, etc.).
  • CRM writes or push to Salesforce / HubSpot.
  • Cross-run dedupe. Each run is independent. The SDR is responsible for merging lists across runs.

Setup

See references/places_api_setup.md for how to enable Places API (New), create a key, and set GOOGLE_MAPS_API_KEY.

The scrape fallback needs Playwright with Chromium:

pip install -r scripts/requirements.txt
python -m playwright install chromium

Do not run the scrape against Google Maps in CI or on a shared IP without understanding that it violates Google's Terms of Service.

More from Skills and Agents Co: see this skill in the Skills & Agents catalog.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.