Simple Random Interaction Designer
PassAudited by ClawScan on May 10, 2026.
Overview
This skill appears to be a simple local randomizer for optional proactive chat pings, with disclosed but noticeable use of available context sources for some message types.
This skill is safe-looking and lightweight, but it is meant for recurring proactive messages. Before installing, make sure you are comfortable with the agent occasionally using recent chat or available integrations such as calendar, weather, or smart-home data to compose casual check-ins.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A scheduled casual ping could cause the agent to look up live context from available tools before composing a message.
This authorizes follow-on tool or integration use during proactive checks. It is disclosed and aligned with data-aware message types, but the phrase is broad enough that users should ensure only intended integrations are available.
If the selected interaction is data-aware, use any relevant OpenClaw-accessible tools, skills, or integrations to fetch live context before drafting the message.
Keep OpenClaw integrations scoped to sources you are comfortable using for proactive messages, and require approval for sensitive tools if the platform supports it.
The agent may reference recent personal conversation details in a casual check-in.
The skill may reuse recent conversation details in proactive messages. The instructions limit this to clearly present context and warn not to fabricate, so this is purpose-aligned but privacy-relevant.
Prefer recent chat context when it is clearly present.
Use this only if you are comfortable with recent chat context being reflected in proactive messages; avoid enabling it in highly sensitive conversations.
Proactive messages may feel spontaneous or human-like rather than explicitly automated.
The final message is intentionally framed as natural and casual rather than explaining that it came from a random scheduled process. This is disclosed in the skill and paired with low-pressure wording, but users should be aware of the presentation choice.
Do not mention the random process, scheduled checks, or why this interaction was selected.
Install only if you want this style of casual proactive outreach; consider adding disclosure in your own agent settings if you prefer transparency.