i-am

Before installing or enabling this skill, consider the following: - This skill reads your OpenClaw conversation session files (~/.openclaw/agents/main/sessions) and may load unbounded historical messages on first run — if you don't want your past conversations analyzed or included, do not install. - The skill proposes creating/modifying a cron-tasks.json entry to run automatically twice daily. If you prefer no background activity, choose the manual mode and verify cron entries before enabling them. - The description references 'IM-adaptive file sending' and the instructions parse message metadata; clarify exactly where generated/backup files (USER.md, ChangeLog.md) will be sent, to whom, and whether any data will leave your machine or be posted externally. If this is not explicit, assume it could be transmitted and avoid installing. - Ask the publisher for a minimal, auditable runtime flow: explicit consent prompts before first data access, a configurable message-history limit, a dry-run that shows extracted messages before analysis, and an opt-out for automatic scheduling. - If you still want the functionality: run in manual mode, inspect the created files and cron-tasks.json yourself, and consider running the skill in a restricted/testing account or environment first. My confidence is medium because the skill is internally coherent for its stated goal, but the combination of broad local data access, automatic scheduling, and implied adaptive sending is disproportionate without clearer consent and data-exfiltration controls. Additional information that would raise confidence toward 'benign': explicit, user-visible consent prompts; a clear, auditable description of any sending behavior (endpoints/recipients); and configurable limits on how much history is read on first run.