Prepare Slack messages directly in the user's own composer for channels, direct messages, or thread replies. Drafts use the user's connected Slack account and remain unsent until the user reviews and sends them.
Create Slack message drafts in the user's own composer, as the user, through their per-user Slack OAuth. Drafting only — the user reviews and sends from Slack.
Review the instructions the agent will receive before you install.
Use this skill when the user wants a Slack message prepared for them to review and send themselves: "draft a reply to X", "prep a message for #general", "write that up as a Slack draft". The draft lands in their own Slack composer, attributed to them, targeted at the conversation you choose — nothing is posted.
This is an OAuth connector. The resolved user's Slack user token lives on your
computer as $VAULT_TOKEN_SLACK_COM. Do not ask the user for a token, log it, or
use another principal's. If the variable is empty or Slack returns 401/403, the user
either has not connected Slack or connected before this permission existed — tell
them to (re)connect it through the product OAuth flow.
Use the bundled helper for every draft — it owns destination resolution, rich-text block construction, and the required draft envelope:
Run these commands with execute and an explicit sandbox_id, using the absolute
directory reported by the skill read in place of <skill dir>. Keep that ID for
preparing body files and running the helper.
python3 "<skill dir>/scripts/slack_drafts.py" create --to '#general' --text 'hello'
python3 "<skill dir>/scripts/slack_drafts.py" create --to '@jane' --text-file body.txt
python3 "<skill dir>/scripts/slack_drafts.py" create --to C0123ABCDEF --thread-ts 1712345678.000100 --text '...'
python3 "<skill dir>/scripts/slack_drafts.py" resolve --to '#general'
--to takes a channel/IM ID (C…/G…/D…), a user ID (U…/W…), #channel-name,
or @name (matched against username, display name, real name, or email; ambiguous
matches are refused — fall back to a user ID).--thread-ts targets the draft at a thread reply instead of the channel composer.im:write scope; tokens connected before that
scope existed can only draft into conversations that already exist. On a
missing_scope error, tell the user to reconnect Slack.attached_draft_exists. Tell the user to send or discard the
existing draft, then retry.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Help QM organization admins inspect settings, stored memory, conversations, files, and operational records across the organization. It also supports confirmed configuration changes and external user management, while keeping admin grant changes in the dashboard.
Carry out website tasks in a remote browser, including expense submissions, authorized orders, and retrieving data behind a login. Personal browser profiles preserve sign-ins, while users handle login and verification screens themselves.
Sign in to a cloud provider’s command-line tool using a verification URL and one-time code approved on the user’s device. Check installation and account identity, save the login, and run commands within that user’s permissions.
Help users discover and connect apps, then run available app tools through QM’s authenticated backend. It checks connection status, presents consent options, and keeps Composio project keys out of user-facing setup.
Connect supported work apps through browser consent without sharing passwords with the agent. The skill checks available connection methods, provides a single-use authorization link when appropriate, and guides personal Slack account linking.
Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.