Slack Automator

Automate Slack messaging, channels, and search with Block Kit. Use when sending scheduled messages, syncing channels, monitoring chats, notifying teams.

This skill appears to do what it claims, but review and take these precautions before installing/using it: - Inspect the included script (scripts/script.sh) yourself before running. It will create ~/.slack-automator and write config.json, history.json, schedule.json, and template files there. - The Slack webhook URL is stored in plaintext at ~/.slack-automator/config.json. Use a webhook that is scoped to a single channel and rotate it if needed. Set file permissions (chmod 600 ~/.slack-automator/config.json) to limit local access. - The script uses python heredocs with shell-interpolated variables. Avoid passing untrusted content into template save/use or schedule commands to reduce risks from malformed input; prefer simple text values. - The schedule feature only stores cron data locally; you must create your own cron job to trigger sends. Be careful when enabling automated scheduled sends to production channels. - If you need stronger security or auditing, consider using a Slack app with scoped OAuth tokens and finer permissions rather than a shared incoming webhook. If you want me to, I can (a) point out specific lines in scripts/script.sh that would be worth hardening, or (b) produce a checklist of commands to safely inspect and set permissions for the files the skill creates.

Type: OpenClaw Skill Name: slack-automator Version: 4.0.0 The script 'scripts/script.sh' contains multiple critical command injection vulnerabilities where shell variables are unsafely interpolated into Python heredocs (e.g., in _json_set, _build_payload, and _record_history). Because the script uses triple quotes (e.g., """$value""") to pass data to Python without escaping, an attacker could execute arbitrary Python code by providing a message or configuration value containing triple quotes and Python commands. While this appears to be a significant architectural flaw rather than intentional malware, it represents a high-risk execution environment.