slack-automation
Automate Slack Workflows with Rube MCP
Slack operations often require repeated searches, message updates, and channel checks. This skill guides AI agents through Rube MCP workflows for reliable Slack automation.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "slack-automation" from https://skillstore.io/skills/sickn33-slack-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-slack-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "slack-automation". Send a launch reminder to #marketing.
Expected outcome:
The skill resolves #marketing, posts the approved reminder, and returns the channel plus message timestamp for follow-up edits.
Using "slack-automation". Find messages about a delayed release from last week.
Expected outcome:
The skill searches Slack, opens relevant threads, and summarizes matching conversations with channel names and message times.
Using "slack-automation". React to the deployment complete message with a check mark.
Expected outcome:
The skill locates the target message, verifies the channel and timestamp, then adds the requested reaction.
Security Audit
Medium RiskMost static command findings are false positives caused by Markdown code spans around Slack and Rube tool names, not executable shell commands. The real residual risk is the intentional third-party Rube MCP connection, which can process Slack OAuth, workspace messages, and user data. No prompt injection or malicious social engineering was found in SKILL.md.
Confirmed security concerns (1)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (93)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-slack-automation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-slack-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-slack-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-slack-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-slack-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). slack-automation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-slack-automation/audits/4BibTeX citation
@techreport{sickn33-sickn33-slack-automation-2026,
author = {sickn33},
title = {slack-automation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-slack-automation/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "slack-automation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-slack-automation/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-slack-automation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Coordinate Incident Updates
Post clear status updates, reply in existing threads, and preserve message timestamps for later edits.
Find Engineering Context
Search Slack for release, deployment, or incident discussions and expand the most relevant threads.
Schedule Team Announcements
Resolve the correct channel, prepare announcement text, and schedule delivery within Slack limits.
Try These Prompts
Post this message to #team-updates: The maintenance window starts at 18:00 UTC. Confirm the channel before sending.
Search Slack for recent messages about the payment incident in #support, then open the most relevant thread.
Schedule a reminder in #release for tomorrow at 09:00 UTC about the release checklist review.
Find messages from the last seven days about failed deployments, group them by channel, and suggest which threads need follow-up.
Best Practices
- Confirm channel and user identity before any write action.
- Use thread timestamps when replying so updates stay attached to the right conversation.
- Honor Retry-After responses and paginate until Slack returns no cursor.
Avoid
- Posting to channels based only on display names or partial matches.
- Reading broad message history when a scoped search would answer the task.
- Ignoring Slack OAuth scope errors or rate-limit responses.