Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Slack Automator
v4.0.0Automate Slack messaging, channels, and search with Block Kit. Use when sending scheduled messages, syncing channels, monitoring chats, notifying teams.
⭐ 0· 446·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included script and SKILL.md. The script implements connecting to a Slack Incoming Webhook, sending messages, templates, and a local schedule store — all coherent with 'Slack Automator'. Required tools (bash, curl, python3) are reasonable for the described functionality.
Instruction Scope
SKILL.md and the script only read/write files under the user's home directory (~/.slack-automator) and perform HTTP POSTs to Slack webhooks. The instructions do not request unrelated files or environment variables. Note: the script embeds user-provided values into Python heredocs via shell interpolation; if you feed untrusted input into commands that save/format templates or schedule messages, malformed input could break the Python snippets or produce unexpected output. This is a local input-safety concern rather than evidence of malicious behavior.
Install Mechanism
No install spec or remote downloads — the skill is instruction-only and ships a local bash script. Nothing is fetched from external arbitrary URLs during installation.
Credentials
The skill requests no environment variables or external credentials; it stores a Slack Incoming Webhook URL locally in ~/.slack-automator/config.json. That is proportionate to its purpose (sending webhook messages).
Persistence & Privilege
The skill persists configuration, history, templates, and schedules under ~/.slack-automator. This is expected for the feature set but gives the script permanent presence in the user's home directory. It does not request platform-wide privileges or modify other skills.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk979baa12jf0q0fnfdd0ptq0h1837kz0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.