fix: make property-assessor safer for whatsapp runs

skills/web-automation/SKILL.md

@@ -76,6 +76,11 @@ pnpm rebuild better-sqlite3 esbuild
 - Authenticate: `npx tsx auth.ts --url "https://example.com/login"`
 - Natural-language flow: `npx tsx flow.ts --instruction 'go to https://example.com then click on "Login" then type "user@example.com" in #email then press enter'`
 
+Messaging rule:
+- For WhatsApp or similar chat-driven runs, prefer native `web_search`, `web_fetch`, and bounded browser actions over shelling out to these helper scripts for every core step.
+- Treat the dedicated Zillow/HAR scripts as local/manual helpers, regression checks, or non-chat fallbacks.
+- If a messaging workflow needs a subprocess at all, reserve it for a single final delivery step rather than the whole assessment.
+
 ## OpenClaw Exec Approvals / Allowlist
 
 If OpenClaw prompts for exec approval every time this skill runs, add a local approvals allowlist for the main agent before retrying. This is especially helpful for repeated `extract.js`, `browse.ts`, and other CloakBrowser-backed scrapes.
@@ -154,6 +159,7 @@ The photo scripts are purpose-built for the common `See all photos` / `Show all
 - click the all-photos entry point
 - wait for the resulting photo page or scroller view
 - extract direct image URLs from the rendered page
+- fail fast with a timeout instead of hanging indefinitely when the browser-backed extraction stalls
 
 Output is JSON with:
 - `requestedUrl`