quarry-parcelslisted
Install: claude install-skill Fusion-Data-Company/underwriter-os
# Quarry — Parcel Data
A parcel data engine, once the user connects one (their own Quarry account, or an equivalent). When anyone asks about a property and a source is connected, **this is where the answer comes from** — not a paid lookup site, not a map they have to click. Claude queries it and returns the facts.
## Setup (once, per firm)
This needs the user's own base URL / key, set in `config/.env` (see `config/.env.example` and `config/CONFIG-GUIDE.md`). If nothing is connected yet, tell the user plainly and offer to walk them through it — don't silently pretend the data exists.
## HARD LAW
If they ask for parcel data and a source is connected, **just get it and give it to them.** Don't open a map, don't explain how, don't ask them to do anything. Run the query, read back the answer, and put it in the one-pager/deal folder.
## How (Claude runs this; user does nothing once connected)
```bash
# by address (auto-geocodes)
python underwriter-os/skills/quarry-parcels/quarry_lookup.py --address "ADDRESS, CITY STATE"
# by coordinates
python underwriter-os/skills/quarry-parcels/quarry_lookup.py --lat 00.00 --lng -00.00
# everything in a map area (returns a list — no map shown)
python underwriter-os/skills/quarry-parcels/quarry_lookup.py --bbox "minLng,minLat,maxLng,maxLat" --limit 200
```
The base URL comes from the user's own `config/.env`. It returns JSON — owner, mailing address, absentee flag, county, APN, acreage, lot sqft, zoning, year built, building sqft, units, and v