repair-reader
Skill2 starsChanged 14 days agoMITView on GitHub
Fix one of sg-stay-where's site readers (browser/propertyguru.js, browser/99co.js, browser/carousell.js) when a listing site changes its pages. Use when a reader returns kind "none", an error, zero cards on a page that shows listings, or listings missing price, postal code, photos or the agent's number.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-searchSkill
- one-chat-many-homesSkill
- schedule-pollsSkill
- uninstallSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Find what moved: Run the reader and look at what it returns.
- Distinctive: line 42
Keep to the browsing rules while you do this: one tab, a few page loads, and stop at any human check.
≈ “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
Repair a site reader
The readers are plain functions the agent runs inside the user's browser on a listing site's page. They read the page's structured data and return tracker-shaped listings. They break when a site moves that data. Fix them against the live page; never fetch listing pages from the server.
| Reader | Search pages | Listing pages |
pgExtract (browser/propertyguru.js) | __NEXT_DATA__ → props.pageProps.pageData.data.listingsData[].listingData | __NEXT_DATA__ listingData, detailsData.metatable, contactAgentData, listingLocationData |
n99Extract (browser/99co.js) | cards: links to /singapore/(rent|sale)/property/…, card text, JSON-LD ItemList | JSON-LD Product, the facts line under the h1, the agent's whatsapp_number in script data |
cxExtract (browser/carousell.js) | cards: links to /p/<slug>-<id>/, card text | JSON-LD Product and BreadcrumbList, label/value lines (Postal Code, Estate, Mobile Number) |
Steps
- Rule out the page first. In the user's Chrome, look at the page. If it
shows a CAPTCHA, a login wall, an empty search or an error, the reader isn't
the problem. Stop and tell the user, or fix the search instead
(
skills/build-search). - Find what moved. Run the reader and look at what it returns. Then inspect
the live page with small JavaScript checks: does the data path still exist
(
__NEXT_DATA__, JSON-LD types, link patterns, label text)? Compare a field the reader gets wrong with where the page now shows it. Read only what you need; don't dump whole pages into the conversation. - Make the smallest change in that reader. Keep its output shape
(
{ kind, listings: [...] }and the field names). Prefer structured data (embedded JSON, JSON-LD) over screen text. Keep rent and sale pages both working: patterns like/(rent|sale)/and prices with or without/mo. - Check the edited reader on the live site. Load the edited source into the page the way docs/polling.md step 1.2 describes, then run it on one search page and one listing page. Confirm the counts, and that price, type, size, postal code and the agent's number come through.
- Run
npm test, commit on a branch with a message that says what the site changed and when you checked it, and tell the user. Don't run a full poll to test it; one search page and one listing page are enough.
Keep to the browsing rules while you do this: one tab, a few page loads, and stop at any human check.
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.

