← Back to Skills Marketplace
8392
Downloads
7
Stars
0
Active Installs
24
Versions
Install in OpenClaw
/install slack-api
Description
Slack API integration with managed OAuth. Send messages, manage channels, search conversations, and interact with Slack workspaces. Use this skill when users want to post messages, list channels, get user info, or automate Slack workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Slack connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Slack action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Slack examples; they add no Slack capability - Slack is itself an event source, so its own events are in `references/slack/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to authorize Slack through Maton. Review every requested write, function deployment, trigger, or destination carefully, keep triggers narrowly scoped, and avoid raw MATON_API_KEY use unless the CLI cannot be installed.
Capability Assessment
Credentials
Network access, Bash, and OAuth/API credentials are proportionate for a Slack API skill, with guidance to avoid inspecting stored credentials and to limit raw API key use.
Install Mechanism
Installation uses a pinned Maton CLI via npm or Homebrew and no packaged executable scripts were present in the artifact.
Instruction Scope
Instructions repeatedly default to read/list operations, require explicit approval for writes, connections, functions, triggers, and destinations, and treat third-party content as untrusted.
Persistence & Privilege
OAuth tokens, hosted functions, triggers, and destinations can persist, but the artifact discloses this, scopes it to user-approved workflows, and includes deletion/revocation guidance.
Purpose & Capability
The skill's Slack read/write, channel, file, search, function, and trigger capabilities match its stated Slack integration and automation purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install slack-api - After installation, invoke the skill by name or use
/slack-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.10
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.9
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.8
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.7
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.6
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.5
Harden every multipart upload example: the assembled request body now goes to an owner-only file created with umask 077 and mktemp, removed by a trap on any exit, instead of a predictable shared /tmp path that could be pre-created by another user and left behind holding a copy of the uploaded file
v1.2.4
- Removed the skill-card.md file.
- No changes to functionality or documentation in SKILL.md.
v1.2.3
Fix the raw HTTP fallback example: restore the gateway base URL in the GATEWAY constant (and the fastmail streaming call), which a previous edit had replaced with a placeholder
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.11
- Removed the file: skill-card.md
- No user-facing features or interface changes introduced in this version.
v1.0.10
- Added CLI usage examples for all supported features, including message and connection management.
- Included instructions for installing the Maton CLI via NPM and Homebrew.
- Expanded Quick Start and Authentication sections with both CLI and Python examples.
- Provided CLI and Python examples side-by-side for connection management tasks.
- API Reference now includes parallel CLI commands for common operations.
- Improved overall organization for easier navigation and usage.
v1.0.9
- Updated all endpoint URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for a unified API entrypoint.
- Security & Permissions section added, emphasizing user confirmation for all write operations.
- Connection management documentation updated to reflect new endpoints.
- LICENSE.txt was removed from the repository.
v1.0.8
- Expanded and reorganized the API Reference section to include additional Slack endpoints (such as scheduling messages, channel management, setting topics/purposes, etc.).
- Improved documentation structure by grouping related endpoints and providing clearer headings for each category.
- Added new examples and options for conversations, including create, join, leave, archive, unarchive, rename, set topic, and set purpose endpoints.
- Updated metadata: added homepage field and adjusted emoji value formatting.
v1.0.7
- Added new metadata section under `clawdbot`, specifying requirements and an emoji.
- No functional changes to API or usage—documentation metadata update only.
v1.0.6
- No file changes detected in this version.
- No user-facing changes; documentation and functionality remain the same as previous version.
v1.0.5
Version 1.0.5 of the slack-api skill
- No file changes were detected in this version.
- Functionality and documentation remain the same as the previous release.
v1.0.4
- All shell-based usage and management examples have been replaced with embedded Python one-liners using the standard library for HTTP requests.
- Updated Quick Start and Connection Management sections to feature Python automation instead of curl commands.
- No changes to the API endpoints or general documentation content.
- JavaScript and Python code samples remain available for advanced scripting.
Metadata
Frequently Asked Questions
What is Slack?
Slack API integration with managed OAuth. Send messages, manage channels, search conversations, and interact with Slack workspaces. Use this skill when users want to post messages, list channels, get user info, or automate Slack workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Slack connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Slack action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Slack examples; they add no Slack capability - Slack is itself an event source, so its own events are in `references/slack/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 8392 downloads so far.
How do I install Slack?
Run "/install slack-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Slack free?
Yes, Slack is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Slack support?
Slack is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Slack?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.10.
More Skills