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

Prefer accessible all-photos views for property photo review

Browse Source
This commit is contained in:
Stefano Fiorini
2026-03-27 13:15:06 -05:00
parent 90635bf8f2
commit c2ae79ccf0
2 changed files with 22 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -63,22 +63,25 @@ For the target property, capture when available:
Always look at the listing photos when they are available. Do not rate a property only from structured text.
### Required gallery workflow
### Required photo-access workflow
When the source site has a photo gallery or modal lightbox, you must explicitly open it and verify that you are seeing distinct images, not just a gallery preview tile or repeated screenshot of the first image.
When the source site exposes listing photos, prefer the **most accessible all-photos view** first. This can be:
- a scrollable all-photos page
- a photo grid
- an expanded photo list
- or, if necessary, a modal gallery/lightbox
Use `web-automation` for this. Preferred process:
1. Open the listing page.
2. Click the gallery entry point such as `See all photos`, `See all 29 photos`, or the main hero image.
3. Confirm the gallery/lightbox is actually open.
4. Capture the first image.
5. Advance through the gallery using the actual next-arrow control inside the gallery, not a blind keyboard press unless you have confirmed it changes the image.
6. After each advance, confirm the image changed before treating it as reviewed.
7. Review enough images to cover the key rooms and exterior, and for smaller listings aim to review all photos when practical.
8. If navigation fails, say so explicitly and do not claim that you reviewed all photos.
2. Click the photo entry point such as `See all photos`, `See all 29 photos`, `Show all photos`, or the main hero image.
3. If that opens a scrollable all-photos view, grid, or photo page that clearly exposes the listing images, use that directly for photo review.
4. Only use next-arrow / slideshow traversal when the site does not provide an accessible all-photos view.
5. If you must use a modal/lightbox, verify that you are seeing distinct images, not just a gallery preview tile or repeated screenshot of the first image.
6. Review enough images to cover the key rooms and exterior, and for smaller listings aim to review all photos when practical.
7. If photo access fails or is incomplete, say so explicitly and do not claim that you reviewed all photos.
Minimum honesty rule: never say you "looked at all photos" unless you successfully inspected distinct gallery images one by one.
A gallery landing page, collage view, repeated first image, or a single screenshot of the listing page does **not** count as full photo review.
Minimum honesty rule: never say you "looked at all photos" unless the site actually exposed the full set and you successfully reviewed them.
A gallery landing page, collage preview, repeated first image, or a single screenshot of the listing page does **not** count as full photo review.
### What to inspect in the photos

15
skills/web-automation/SKILL.md
View File

@@ -127,20 +127,21 @@ Example:
npx tsx flow.ts --instruction 'go to https://search.fiorinis.com then type "pippo" then press enter then wait 2s'
```
### Gallery/lightbox workflows
### Gallery/lightbox and all-photos workflows
For real-estate listings and other image-heavy pages, prefer opening the gallery/lightbox explicitly and verifying that each navigation step produces a distinct image.
For real-estate listings and other image-heavy pages, prefer the most accessible all-photos view first.
Practical rules:
- Do not treat a listing page hero image, gallery collage, or modal landing view as full photo review.
- After opening the gallery, capture the first image, then use the actual in-gallery next control.
- Confirm the image changed before counting the next screenshot as reviewed.
- A scrollable all-photos page, expanded photo grid, or photo list is an acceptable source for condition review if it clearly exposes the listing images.
- Do not treat a listing page hero image, gallery collage preview, or modal landing view alone as full photo review.
- Only rely on next-arrow / slideshow traversal when the site does not provide an accessible all-photos view.
- If using a gallery, confirm the image changed before counting the next screenshot as reviewed.
- If a generic `Next` control exits the gallery or returns to the listing shell, stop and adjust the selector/interaction; do not claim the photos were reviewed.
- Blind `ArrowRight` presses are not reliable enough unless you have already verified that they advance the gallery on that site.
- For smaller listings, review all photos when practical; otherwise review enough distinct photos to cover kitchen, baths, living areas, bedrooms, exterior, and any waterfront/balcony/deck elements.
- If automation cannot reliably advance the gallery, say so explicitly in the final answer.
- If automation cannot reliably access enough photos, say so explicitly in the final answer.
Where possible, prefer specific controls over vague ones, for example a gallery-specific next-arrow button rather than a page-level `Next` button.
Where possible, prefer a site’s explicit `See all photos` / `Show all photos` path over fragile modal navigation.
## Compatibility Aliases