Refresh property assessor and web automation docs
This commit is contained in:
84
docs/property-assessor.md
Normal file
84
docs/property-assessor.md
Normal file
@@ -0,0 +1,84 @@
|
||||
# property-assessor
|
||||
|
||||
Decision-grade residential property assessment with required photo review, comp checks, carry-cost underwriting, and explicit buy/pass guidance.
|
||||
|
||||
## What this skill is for
|
||||
|
||||
- Assessing a property from an address, Zillow URL, HAR URL, or other listing source
|
||||
- Reconciling baseline facts across multiple listing/public sources
|
||||
- Reviewing listing photos before making condition claims
|
||||
- Producing a practical verdict such as `buy`, `pass`, or `only below X`
|
||||
|
||||
## Core workflow
|
||||
|
||||
1. Normalize the address and property type.
|
||||
2. Build a baseline fact set from the best available listing or record source.
|
||||
3. Cross-check facts on other sources.
|
||||
4. Review photos before making condition claims.
|
||||
5. Pull comps.
|
||||
6. Underwrite carry costs and risk factors.
|
||||
7. End with a clear verdict and fair-value guidance.
|
||||
|
||||
## Required photo-review workflow
|
||||
|
||||
Photo review is mandatory when a listing source exposes photos.
|
||||
|
||||
Preferred source order:
|
||||
1. Zillow
|
||||
2. HAR
|
||||
3. Realtor.com
|
||||
4. Brokerage mirror or other accessible listing mirror
|
||||
|
||||
Rules:
|
||||
- Do not claim condition from structured text alone when listing photos are available.
|
||||
- Prefer accessible all-photos views, photo grids, or scrollable photo pages over fragile next-arrow traversal.
|
||||
- If the primary source fails but a fallback source exposes the photos, continue with the fallback.
|
||||
- If photo review is incomplete, say so explicitly and lower confidence.
|
||||
|
||||
## Zillow and HAR integration
|
||||
|
||||
This skill now expects the dedicated `web-automation` extractors first.
|
||||
|
||||
### Zillow
|
||||
|
||||
```bash
|
||||
cd ~/.openclaw/workspace/skills/web-automation/scripts
|
||||
node zillow-photos.js "<zillow-listing-url>"
|
||||
```
|
||||
|
||||
Success means:
|
||||
- the Zillow all-photos page opened, or
|
||||
- Zillow's rendered listing shell already exposed the full direct image set and the extracted count matches the announced count
|
||||
|
||||
The returned `imageUrls` are the photo-review set. Review those images before making condition claims.
|
||||
|
||||
### HAR fallback
|
||||
|
||||
```bash
|
||||
cd ~/.openclaw/workspace/skills/web-automation/scripts
|
||||
node har-photos.js "<har-listing-url>"
|
||||
```
|
||||
|
||||
Use HAR when Zillow does not expose a reliable photo set. The returned `imageUrls` are the review set for the fallback path.
|
||||
|
||||
## Approval-safe command shape
|
||||
|
||||
For chat-driven runs, prefer file-based commands under `~/.openclaw/workspace/skills/web-automation/scripts`.
|
||||
|
||||
Good:
|
||||
- `node check-install.js`
|
||||
- `node zillow-photos.js "<url>"`
|
||||
- `node har-photos.js "<url>"`
|
||||
|
||||
Avoid when possible:
|
||||
- `node -e "..."`
|
||||
- `node --input-type=module -e "..."`
|
||||
|
||||
## Output requirements
|
||||
|
||||
The final assessment should explicitly include:
|
||||
- `Photo source attempts: ...`
|
||||
- `Photo review: completed via <source>` or `Photo review: not completed`
|
||||
|
||||
If photo review was completed, briefly summarize the condition read from the photos.
|
||||
If not, mark condition confidence as limited and explain why.
|
||||
Reference in New Issue
Block a user