build-search
Skill2 starsChanged 14 days agoMITView on GitHub
Build or repair a listing-site search for sg-stay-where in the user's own Chrome, by setting the site's own filters and saving the address bar. Use for every buying project, for rental filters the search template can't express (property type, MRT station, tenure), and when a saved search returns no cards or ignores a filter because a site changed its URLs.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- one-chat-many-homesSkill
- repair-readerSkill
- schedule-pollsSkill
- uninstallSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 23
Use the user's own Chrome, in one tab, at browsing pace.
- Distinctive: line 27
Never fetch listing sites from the server or a script.
- Very specific: line 28
Never invent filters. Use what the interview recorded (docs/setup-interview.md).
- Very specific: line 70
If the URL is right but the reader returns nothing, the page changed instead: follow skills/repair-reader.
≈ “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.
Files
Build a search on the site
The tracker polls saved search URLs. Rather than guessing a site's URL parameters, let the site write the URL: open its search page in the user's Chrome, set the filters with its own controls, and save what the address bar shows. This also works when a site renames its parameters.
When to use it:
- Buying projects (
"deal": "buy"). The search template only builds rental searches, so every buying search is built this way. - Renting, when the template can't express a filter: HDB only, one MRT station, a project, PropertyGuru's floor or furnishing filters.
- Recovery. A search returns
no listing cards found, or its results ignore a filter, such as prices outside the range or the wrong property type.
Rules
- Use the user's own Chrome, in one tab, at browsing pace. If a page needs a human (a CAPTCHA that doesn't clear by itself, or a login), stop and tell the user. Never work around it. Cloudflare's "Just a moment" page clears in 5–10 s; wait, don't click.
- Never fetch listing sites from the server or a script.
- Never invent filters. Use what the interview recorded (docs/setup-interview.md); ask the user when something is missing.
Steps
- Read the project:
node src/cli.js api GET /api/state?project=<id>. Noteproject.deal, the budget, home type, areas and districts, and any existing searches. - Open the site's search page for that deal (starting points are below).
- Set the filters with the site's controls, not by editing the URL: price range, property type (HDB, condo or EC, landed), bedrooms, area, and tenure when the site has it. Filter panels change as you choose: on PropertyGuru, picking HDB adds a sub-type row (an HDB 4-room is the usual 3-bedroom flat), so look again after every click. Then read the address bar. The server sorts it newest first and drops any page number it carries, because polls read only the first pages and add their own.
- Check it with the site's reader on page 1 (docs/polling.md step 1.2 shows
how to load
pgExtract,n99ExtractorcxExtract). There must be cards (r.listings.length > 0), prices inside the range, and types that match. If not, adjust the filters and check again. - Save it.
- One search:
node src/cli.js api POST /api/projects/<id>/searches '{"title":"PropertyGuru · 4-room HDB, east","url":"<address bar>","pages":5}' - A set that replaces earlier ones (one per site, keeping each one's
on/off switch): send them in a sourcing plan as
searches(docs/sourcing.md):[{ "url": "…", "title": "…", "districts": ["D16","D18"], "why": "99.co has no district filter" }]. Givedistrictsto a 99.co search so its reader keeps only cards in them, by postal code.
- One search:
- Tell the user what each search covers and what the site couldn't filter. They switch searches on and off in the Searches tab.
Repairing a broken search
- Open the saved URL and see what the site does with it: an error page, all of Singapore, a dropped filter.
- Rebuild it with steps 3–4, then update it:
node src/cli.js api PATCH /api/projects/<id>/searches/<search id> '{"url":"<new address bar>"}'. - A rental template search (its
templateismainand the project is renting) gets its URL fromsrc/searches.js. Fix the builder there to match the URL the site produced, updatetest/searches.test.jswith that URL, and re-apply the template. If you aren't sure, save the hand-built URL as its own search, switch the broken one off, and tell the user. - If the URL is right but the reader returns nothing, the page changed instead:
follow
skills/repair-reader.
Done this way on 31 Oct 2026 for a buying project (HDB 4-room, 3 bedrooms,
S$500–800k on PropertyGuru): the site wrote
property-for-sale?listingType=sale&isCommercial=false&minPrice=500000&maxPrice=800000&propertyTypeGroup=H&propertyTypeCode=4A&…&bedrooms=3;
page 1 read 25 HDB 3-bedroom cards at S$505k–780k, and a poll took one through
details and Google Maps into Review.
Starting points (checked in Chrome, 31 Oct 2026)
| Site | Renting | Buying |
| PropertyGuru | https://www.propertyguru.com.sg/property-for-rent?listingType=rent&isCommercial=false&minPrice=…&maxPrice=… | https://www.propertyguru.com.sg/property-for-sale?listingType=sale&isCommercial=false&minPrice=…&maxPrice=… |
| 99.co | https://www.99.co/singapore/rent?main_category=all&property_segments=residential&price_range=MIN,MAX | https://www.99.co/singapore/sale?main_category=all&property_segments=residential&price_range=MIN,MAX |
| Carousell | https://www.carousell.sg/categories/property-102/rent-in-singapore-229/?price_start=…&price_end=… | https://www.carousell.sg/categories/property-102/property-for-sale-230/?price_start=…&price_end=… |
These are only starting points. Add the rest of the filters with each site's own
controls. 99.co has no district filter, so use districts. Carousell filters
price and bedrooms only; the skip rules and postal codes do the rest once each
listing page is read.
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
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.

