Add apify-zillow-real-estate-leads skill - #73
Open
afanasenkoa wants to merge 2 commits into
Open
afanasenkoa wants to merge 2 commits into
afanasenkoa wants to merge 2 commits into
Conversation
Real-estate lead building from Zillow, ordered by what the listing scrape already returned rather than by what an enrichment actor could find. The listing agent's contact details ship inside the property row, and agentEmailSource says which lookup produced the email. Measured across 75 for-sale listings in three markets on 2026-07-29: cell phone present on 75 of 75, email on 61 of 75 (Austin 92%, Chicago 84%, Miami Beach 68%). So the skill uses Google Search plus a contact scraper only for the ~1 row in 5 with no email, instead of routing every lead through a Maps email extractor. Also documents three things that are easy to get wrong: filters apply in ZIP mode only, a ZIP is searched as its city so results span the metro, and the property cap covers a batch of up to five ZIPs rather than each one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Two of the traps this skill documented were fixed upstream today (afanasenko/zillow-property-agent-data-scraper 2.3.84, and the ZIP-only and MCP siblings): a ZIP is no longer searched as its city, and the property cap now applies per ZIP rather than to a batch of five. Replaces both with what an agent now needs to know — that cost scales with the ZIP list, and that the handful of ZIPs Zillow cannot search directly fall back to a city search filtered back to the ZIP, reported in RUN_SUMMARY.zipScope. The measured contact-yield numbers (phone 100%, email 81% across 75 listings) are unchanged; only the ZIP-scope claims moved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Skill
apify-zillow-real-estate-leadsChecklist
skills/apify-<name>/(no other file changes except.claude-plugin/marketplace.json)SKILL.mdfrontmatter hasname(matches folder,apify-prefix) anddescription(838 chars).claude-plugin/marketplace.jsonNotes
Why this niche. Neither this repo nor
apify/agent-skillsmentions Zillow anywhere today — the real-estate routing table inapify-ultimate-scrapercovers Redfin and an aggregator only. This fills that gap rather than competing with an existing skill.The insight it leads with is measured, not estimated. 75 for-sale listings across three markets on 2026-07-29:
cellPhoneagentEmailBecause the agent's contact is already in the listing row, the skill treats Google Search + a contact scraper as tiers 2 and 3 for the ~19% remainder, rather than routing every lead through a Maps email extractor. It also documents three things that are easy to get wrong: input filters apply in ZIP mode only, a ZIP is searched as its city so results span the metro, and the property cap covers a batch of up to five ZIPs rather than each one.
Heads-up on CI, unrelated to this PR.
scripts/generate_agents.pycurrently fails on a cleanmain:skills/apify-x402-agentic-wallet/landed in #59 without itsmarketplace.jsonentry. I verified this by stashing my changes and re-running the validator on pristinemain, so it is not introduced here — but it will likely make this PR's check red too. I left it alone to keep this PR to one skill; happy to open a separate one-line PR adding the missing entry if that would help.bash scripts/lint_telemetry.shpasses.