Home/stef-openclaw-skills
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Keep Zillow photo workflow inside web-automation

Browse Source
This commit is contained in:
Stefano Fiorini
2026-03-27 16:17:45 -05:00
parent 35d3fede49
commit e7c56fe760
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
skills/property-assessor/SKILL.md
View File

@@ -149,6 +149,10 @@ If Zillow exposes a page with a scroller that shows the listing photos, that pag
If that scroller page exposes direct image links such as `https://photos.zillowstatic.com/...`, treat those URLs as successful photo access and use that image set for review.
This is preferred over fragile modal next/previous navigation.
For this normal Zillow all-photos workflow, stay inside **`web-automation` only**.
Do **not** escalate to coding-agent, ad hoc Python helpers, or extra dependency-heavy tooling just to open `See all photos`, inspect the scroller page, or extract Zillow image URLs.
Only escalate beyond `web-automation` if `web-automation` itself truly cannot access the all-photos/scroller page or the exposed image set.
Do not rely on generic page text, photo counts, or non-photo shells as a Zillow attempt.
Only fall back to HAR/Realtor/broker mirrors if the Zillow all-photos path was actually attempted with `web-automation` and did not expose the photos reliably.
A source only counts as an attempted photo source if you actually did one of these: