Reaction Processor

Record real OpenClaw events and reactions for the current closed-loop workflow. Use for logging duplicate-skipped and proposal-created outcomes in public.ope...

This script appears to do what it says (recording trigger events/reactions), but review the following before installing or running: 1) It runs docker exec into a container named 'supabase-db' and runs psql there — ensure you trust the runtime environment and that the agent is not given unnecessary Docker daemon access. 2) The DB container name, postgres user, database name, and AGENT_ID are hardcoded; consider requiring these as explicit config/env vars and avoid running on production without a backup. 3) Inspect the SQL to confirm you are comfortable with the inserts/updates to public.openclaw_* tables. 4) If you want least privilege, run the script in a test environment first or adapt it to use a less-privileged DB user and to accept connection details via environment variables rather than hardcoded values.

Type: OpenClaw Skill Name: reaction-processor Version: 1.0.0 The skill bundle is designed to log workflow events and reactions for a 'stale missions' alert system. The primary script, scripts/reaction-processor.sh, interacts with a local Supabase database via docker exec to update internal tables (public.openclaw_agent_events, public.openclaw_agent_reactions). The logic is consistent with the stated purpose in SKILL.md, contains no external network calls or data exfiltration, and uses a hardcoded AGENT_ID rather than unsanitized user input for its SQL operations.