菜单
How to use the Slack connector's tools — sending and scheduling messages, replying in threads, reading channel history, searching the workspace, adding reactions, and resolving channels and users. Use when the user works with Slack, channels, DMs, threads, messages, reactions, or wants to post or look something up in a workspace.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
How to use the Dropbox connector's tools — browsing folders, searching, reading file content, creating and moving files, and managing shared links. Use when the user works with Dropbox, cloud files, folders, documents, shared links, file requests, or storage.
How to use the Outlook connector's tools — listing, reading, drafting, sending, replying, and filing mail, plus reading and creating calendar events. Use when the user works with Outlook, Microsoft 365 mail, their inbox, drafts, mail folders, meeting invites, or calendar events.
How to use the Asana connector's tools — finding, creating, and updating tasks, subtasks, comments, and projects, and navigating workspaces and sections. Use when the user works with Asana, tasks, to-dos, projects, assignees, due dates, or team workflows.
How to use the Box connector's tools — browsing folders, uploading and downloading files, copying, sharing via links, commenting, and asking Box AI questions about file contents. Use when the user works with Box, files, folders, documents, shared links, or cloud storage.
How to use the Cloudflare connector's tools — listing and inspecting Workers, managing KV namespaces, R2 buckets, D1 databases, and Hyperdrive configs, and running SQL against D1. This is the Workers Bindings server, scoped to one Cloudflare account. Use when the user works with Cloudflare, Workers, KV, R2, D1, Hyperdrive, edge storage, or serverless bindings — NOT DNS records, zones, WAF, page rules, or CDN/cache settings (this server does not expose those).
How to use the GitHub connector's tools — finding repositories, reading repos, READMEs, branches, and commits, and creating and managing issues, pull requests, reviews, comments, labels, assignees, and file contents. Use when the user works with GitHub, repos, issues, PRs, pull requests, code reviews, branches, commits, or wants to open an issue or PR.
| name | slack |
| description | How to use the Slack connector's tools — sending and scheduling messages, replying in threads, reading channel history, searching the workspace, adding reactions, and resolving channels and users. Use when the user works with Slack, channels, DMs, threads, messages, reactions, or wants to post or look something up in a workspace. |
You are using the Slack connector (via Composio). Its tools act on the connected workspace as the authorized user/bot. Apply this guidance whenever you touch Slack.
channel. Prefer a channel ID (C… public, G…
private, D… DM) over a #name. Name resolution is unreliable and fails
outright on org-wide tokens. Resolve a human reference with the
find-channels tool (SLACK_FIND_CHANNELS, by query) or list-channels before
posting.SLACK_FIND_USER_BY_EMAIL_ADDRESS) or list-users. Mention
in text as <@U012ABC>, not @name.SLACK_SEND_MESSAGE) requires channel and at least one content
field (text, markdown_text, blocks, or attachments) — omitting all
errors with no_text. Keep a message body under ~4000 chars; split or
thread longer content.thread_ts = the parent message's ts (the
original, never a reply's ts). Timestamps are strings with fractional
precision ("1700000000.123456"); pass them exactly as returned.*bold*, _italic_, ~strike~,
> quote, `code`. Links are <url|label>. There are no # headings.ts + channel. To react, add-reaction
(SLACK_ADD_REACTION_TO_AN_ITEM) takes the emoji name (no colons),
channel, and message timestamp.SLACK_FETCH_CONVERSATION_HISTORY) returns the main
timeline only — threaded replies are not included. To read a thread, call
fetch-message-thread with the channel and the parent ts. Page with
cursor; bound with oldest/latest rather than pulling everything.SLACK_SEARCH_MESSAGES) is workspace-wide and uses Slack search
operators, not plain keywords: in:#channel, from:@user,
before:YYYY-MM-DD, after:YYYY-MM-DD, has:link, has::emoji:. Combine
them (deploy in:#eng from:@alice after:2026-01-01) instead of fetching broad
and filtering yourself. Search only sees content the connected identity can
access.C… id, public vs. private) and the
content before sending, especially for @here/@channel or cross-channel posts.@channel, @here) unless asked — it notifies
everyone. Scheduled messages (SLACK_SCHEDULE_MESSAGE, post_at = future
Unix time) still fire later; say so when you set one.Retry-After). When in
doubt about which channel, ask rather than guessing — a wrong-channel post is
user-visible and hard to undo cleanly.