realtyapi/realtyapi-skills / skills/listing-search
listing-search
VerifiedUse when the user wants to find for-sale (or sold) homes matching criteria in an area — location, price range, beds/baths, home type, status. Searches the right portal(s) with filters, paginates, and returns a ranked, de-duplicated listings table with source links. Triggers on "find houses in …", "search for 3-bed homes under $500k", "what's for sale in …", "show me recently sold homes near …".
Listing Search
Overview
Find homes for sale (or recently sold) that match the user's criteria in a given area, and return a clean, ranked shortlist with links — not raw JSON.
Use realtyapi-api for auth and endpoint discovery.
When to Use
- "Find 3-bed houses under $600k in Austin."
- "What condos are for sale near this zip with a pool?"
- "Show recently sold homes on this street."
- Building a buyer's shortlist or a market scan for an area.
Workflow
- Clarify criteria if missing the essentials: location, buy vs. rent vs. sold, price range, beds/baths, home type. Don't over-ask — sensible defaults are fine.
- Pick the portal for the location's market (catalog in
realtyapi-api). - Resolve the area — use
autocomplete/locationsto turn a place name into the id/coordinates/polygon the search endpoint expects. - Search with filters — call
search/byaddress|search/bycoordinates|search/bypolygon|search/bymapbounds. Read the endpoint'sopenapi.jsonfor the exact filter params (price, beds, baths, status, home type, etc.). - Paginate to gather enough results (increment
pageor follownextPageCursor) — but cap it and tell the user how many pages/credits you used. - De-dupe and rank by the user's priority (price, $/sqft, newest, size).
- Present the table below. State the filters applied and the result count.
Output Format
# Listings: {criteria} in {area}
Portal: {portal} · Filters: {beds/baths/price/type/status} · {N} results ({pages} pages)
| # | Address | Price | Beds/Baths | Size | $/sqft | Status | Link |
|--:|---------|------:|-----------|-----:|-------:|--------|------|
## Notes
- Sorted by: {criterion}
- Standouts: {best value / newest / etc.}
- Excluded: {dupes / out-of-range, if any}
Common Pitfalls
- Confirm buy vs. rent vs. sold — the wrong status filter returns the wrong set.
- One search covers one portal/market. Don't claim "all listings" — say which portal.
- Respect credits: each page is a request. Cap pagination and report what you used.
- Keep the source link for every row so the user can open the real listing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |