Slack
AdvisoryAudited by Static analysis on May 3, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may be able to post messages, change channels, invite users, or manage files in the connected Slack workspace.
The skill can perform Slack write and management actions that may affect other workspace members. This is disclosed and aligned with the Slack-management purpose.
- Send messages to channels and DMs - Schedule delayed messages - Search messages and conversations - Create and archive channels - Invite users to channels - Upload and manage files
Review each target channel, recipient, file, and channel-management action before approving writes, especially bulk or destructive operations.
Actions may be performed with the Slack permissions granted during OAuth, potentially affecting workspace content and members.
The skill relies on delegated Slack account access through OAuth. This is expected for a Slack integration, but it grants permissions according to the connected account and approved scopes.
ClawLink's hosted page runs the Slack OAuth flow — the user clicks through the Slack login and authorization screen.
Confirm the Slack workspace and OAuth scopes during connection, and revoke the ClawLink Slack connection if it is no longer needed.
Installing the plugin adds an external integration layer that can expose dynamic tools to OpenClaw.
The skill depends on an external plugin that is not included in the provided artifacts. The install is explicit and user-directed, so this is a provenance note rather than a concern.
Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
Install only the intended ClawHub plugin, verify the ClawLink source or verification page if needed, and keep the plugin updated from trusted sources.
Slack connection status, tool calls, and credential-related flows depend on ClawLink as the integration provider.
The skill routes authentication and tool calls through the ClawLink service. The destination is disclosed and purpose-aligned, but it is a sensitive third-party integration boundary.
The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`.
Use this only if you trust ClawLink with the Slack integration flow, and avoid sharing sensitive Slack content unless needed for the task.