Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Force agents to respond to automated messages by using `openclaw agent` instead of `openclaw message send`, ensuring tasks from scripts get agent replies.
Force agents to respond to automated messages by using `openclaw agent` instead of `openclaw message send`, ensuring tasks from scripts get agent replies.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When automated scripts (cron, monitoring) send messages via openclaw message send: Messages appear in chat as "system messages" Agents may treat them as background info, not tasks Agents respond to user messages but ignore automated ones Accountability checks, alerts, and tasks go unanswered
Use openclaw agent instead of openclaw message send for messages requiring agent response: # OLD (agent may ignore): openclaw message send --target -GROUP_ID --message "TASK: Do something" # NEW (agent MUST respond): RESPONSE=$(openclaw agent \ --agent AGENT_ID \ --session-id "agent:AGENT_ID:telegram:group:GROUP_ID" \ --channel telegram \ --message "TASK: Do something" \ --timeout 180) # Send response to chat: openclaw message send --target -GROUP_ID --message "$RESPONSE"
openclaw message send → Creates chat message → Agent sees as "notification" openclaw agent → Triggers actual agent turn → Agent MUST process and respond
Use scripts/send_agent_task.sh: # Simple usage: ~/.openclaw/skills/self-prompt/scripts/send_agent_task.sh \ "AGENT_ID" \ "GROUP_ID" \ "Your task message here"
Use scripts/send_agent_task.py: from send_agent_task import send_and_deliver success, response = send_and_deliver( agent_id="stock-trading", group_id="-5283045656", message="TASK: Analyze current positions", timeout=180 )
For monitoring scripts, separate data delivery from task requests: # 1. Send DATA immediately (informational) openclaw message send --target "$GROUP_ID" --message "📊 Position Data: $POSITIONS" # 2. Send TASK via agent (forces response) RESPONSE=$(openclaw agent \ --agent "$AGENT_ID" \ --session-id "agent:$AGENT_ID:telegram:group:$GROUP_ID" \ --message "Analyze the data above and report findings" \ --timeout 180) # 3. Deliver response openclaw message send --target "$GROUP_ID" --message "📊 Analysis: $RESPONSE"
# Force agent to respond to accountability check send_agent_task.sh "my-agent" "-123456789" \ "ACCOUNTABILITY CHECK: Did you complete the required tasks? Respond with status."
# Force agent to investigate and report send_agent_task.sh "trading-agent" "-123456789" \ "ALERT: Position down 5%. Investigate and report findings."
# Force agent to do research send_agent_task.sh "research-agent" "-123456789" \ "DAILY TASK: Search for news on $SYMBOLS and summarize findings."
The session key follows this pattern: agent:AGENT_ID:CHANNEL:TYPE:TARGET Examples: agent:stock-trading:telegram:group:-5283045656 agent:main:telegram:direct:123456789 agent:assistant:discord:channel:987654321
Location: scripts/send_agent_task.sh send_agent_task.sh AGENT_ID GROUP_ID "message" [timeout] Sends task via openclaw agent Captures response Sends response to group via message send Logs to ~/agent_task.log
Location: scripts/send_agent_task.py from send_agent_task import send_and_deliver success, response = send_and_deliver( agent_id="agent-name", group_id="-123456789", message="Task message", timeout=180, channel="telegram" )
Verify agent is running: openclaw gateway status Check session key format matches your agent/group Increase timeout for long-running tasks
Ensure script sends response via message send after capturing Check GROUP_ID is correct (negative for groups) Verify channel is correct (telegram/discord/etc)
Increase timeout for research/analysis tasks (300-600 seconds) Check if agent is overloaded with concurrent requests
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.