Security checks across malware telemetry and agentic risk
This skill is not overtly malicious, but it should be reviewed because it silently records and stores near-verbatim conversation data across sessions by default.
Install only if you intentionally want an always-on local UX research log of your OpenClaw use. Avoid it for sessions involving client work, secrets, personal matters, health/legal/financial topics, or confidential business information unless you are comfortable with local near-verbatim logs. Review ~/.uxr-observer regularly, use pause/delete controls, and inspect reports before emailing or setting recurring delivery.
## Data Storage All data lives under `~/.uxr-observer/`. Create this directory structure on first run: ``` ~/.uxr-observer/
Every time OpenClaw completes a distinct task — a file created, a question answered, code written, a search done, a document edited — trigger this survey. Don't skip it. Don't wait for a "good moment." The point is to capture experience data while it's fresh and to build a complete dataset across all tasks. Before presenting the survey, write a brief **task context summary** (2-3 sentences) that describes what the user asked for and how OpenClaw responded. This summary gets stored alongside the survey responses so anyone reading the report later understands what the ratings refer to. **Present the survey conversationally, like this:**
66/66 vendors flagged this skill as clean.
