apartment-rental-scraperlisted

Configurable apartment-hunting scraper. Searches Zillow, Zumper, Redfin, Craigslist, Apartments.com (for-rent-by-owner), and HotPads (by-owner) for new rentals matching the budget, city, neighborhoods, and Walk Score threshold set in config.json. Clicks into every listing's detail page to verify unit-level pricing (never trusts card-level price ranges), checks Walk Scores, deduplicates against a persistent local tracker, writes a dated report, and — if enabled in config.json — syncs verified links into a Google Doc shortlist. Trigger this skill when the user says: "run the scraper", "find new listings", "check for new apartments", "any new places", "run rental search", "find me new apartments", "check for updates", "run the apartment search", "any new ones", or similar.
Eobodoechine/apartment-rental-scraper · ★ 0 · Data & Documents · score 70

Install: claude install-skill Eobodoechine/apartment-rental-scraper

# Apartment Rental Scraper You are running the user's personal apartment-hunting pipeline. Your job is to find genuinely new rental listings (studio to any size) that haven't been seen before — verified rents, real Walk Scores, real links. No guessing. No assumptions about price. No recycling old results. The most important rule: **click into every listing detail page before recording any price.** Card-level price ranges are unreliable. The Available Units table on the detail page is the truth. ## First run — check config.json before doing anything else Read `config.json` (in this skill's folder) first. If it still contains placeholder values (`YOUR_CITY`, `YOUR_NAME`, `max_rent: 0`, empty `neighborhoods`, etc.), **stop and tell the user to fill it in** — point them at `README.md` — rather than running a search with meaningless criteria. Every step below reads its parameters from `config.json`; nothing in this file is hardcoded to a specific city, price, or person. ## Browser tool — either Playwright MCP or Claude in Chrome works This skill needs ONE connected browser-automation MCP tool. Either of these is fine — check `config.json`'s `browser_tool` setting, then confirm the corresponding tool is actually connected before starting Step 2: | `browser_tool` value | What it needs connected | Its tool names | |---|---|---| | `"playwright"` | A Playwright MCP server | `browser_navigate`, `browser_snapshot`, `browser_click`, `browser_press_key`, `browser_evaluate` | | `"cla