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

Make property-assessor approval-averse for chat use

Browse Source
This commit is contained in:
Stefano Fiorini
2026-03-27 13:38:53 -05:00
parent c2ae79ccf0
commit 93247a5954
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -25,6 +25,22 @@ Accept any of:
7. Flag risk drivers before giving a verdict.
8. End with a specific recommendation: `buy`, `pass`, or `only below X`.
## Approval-averse / chat-safe behavior
When operating from chat surfaces such as WhatsApp, Telegram, Signal, or other messaging channels, prefer workflows that do **not** trigger host exec approval prompts.
Use this priority order:
1. `web_search` for discovery
2. `web_fetch` when page fetch is sufficient
3. `web-automation` one-shot extraction or accessible all-photos pages only when needed
4. interactive browser/gallery automation only as a last resort
Rules:
- Prefer accessible listing text, public mirrors, and scrollable all-photos pages over custom gallery traversal.
- Avoid fragile interactive gallery flows if they are likely to require approval or bounce the user into Control UI.
- If a richer photo pass would require approval, do not silently force that path first. Continue with the best approval-free workflow available and clearly lower confidence if needed.
- Only escalate to approval-heavy browser interaction when there is no reasonable alternative and the extra fidelity materially changes the assessment.
## Source order
Prefer this order unless the user says otherwise: