skills/slack/SKILL.md
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
npx skillsauth add openclaw/openclaw slackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use slack to react, manage pins, send/edit/delete messages, and fetch member info. The tool uses the bot token configured for OpenClaw.
channelId and messageId (Slack message timestamp, e.g. 1712023032.1234).emoji (Unicode or :name:).to target (channel:<id> or user:<id>) and content.Message context lines include slack message id and channel fields you can reuse directly.
| Action group | Default | Notes | | ------------ | ------- | ---------------------- | | reactions | enabled | React + list reactions | | messages | enabled | Read/send/edit/delete | | pins | enabled | Pin/unpin/list | | memberInfo | enabled | Member info | | emojiList | enabled | Custom emoji list |
{
"action": "react",
"channelId": "C123",
"messageId": "1712023032.1234",
"emoji": "✅"
}
{
"action": "reactions",
"channelId": "C123",
"messageId": "1712023032.1234"
}
{
"action": "sendMessage",
"to": "channel:C123",
"content": "Hello from OpenClaw"
}
{
"action": "editMessage",
"channelId": "C123",
"messageId": "1712023032.1234",
"content": "Updated text"
}
{
"action": "deleteMessage",
"channelId": "C123",
"messageId": "1712023032.1234"
}
{
"action": "readMessages",
"channelId": "C123",
"limit": 20
}
{
"action": "pinMessage",
"channelId": "C123",
"messageId": "1712023032.1234"
}
{
"action": "unpinMessage",
"channelId": "C123",
"messageId": "1712023032.1234"
}
{
"action": "listPins",
"channelId": "C123"
}
{
"action": "memberInfo",
"userId": "U123"
}
{
"action": "emojiList"
}
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------