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.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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:
python3 skills/slack-drafts/scripts/slack_drafts.py create --to '#general' --text 'hello'
python3 skills/slack-drafts/scripts/slack_drafts.py create --to '@jane' --text-file body.txt
python3 skills/slack-drafts/scripts/slack_drafts.py create --to C0123ABCDEF --thread-ts 1712345678.000100 --text '...'
python3 skills/slack-drafts/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.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress) accepts your token when the user you're talking to is an org admin and started this turn themselves. Use when an admin asks you to inspect or change anything org-wide or in another scope, or anyone asks whether they're an admin.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a real stealth browser from your shell — act on websites (order food, file an expense, pull data behind a login), with per-person persistent sign-ins via the provider's managed auth (Kernel, Anchor, or Browserbase — picked by which API key you have). Use for ACTING on a site; to just read a page, use curl/wget first. Requires managed model access and a keychain grant for the browser provider key; follow the missing-key steps below.
日本語の概要は準備中です。原文の説明を表示しています。
Sign a cloud provider's CLI in (AWS, Google Cloud, Azure, or another) with a device-code flow, then run that CLI as the requesting user. Covers checking the CLI is installed, the login that survives the browser round-trip, and the boundaries on cloud writes.
日本語の概要は準備中です。原文の説明を表示しています。
Show the app connection picker or setup widget when users ask to connect apps, reopen setup, or need an app that isn't connected yet. Use QM’s authenticated backend for app discovery, consent, and execution without exposing project keys.
日本語の概要は準備中です。原文の説明を表示しています。
Connect an administrator-enabled SaaS app for a user with a one-time OAuth consent link.
日本語の概要は準備中です。原文の説明を表示しています。
Define a Loop — a durable scaffold that works a queue of recurring tasks autonomously (Sentry issues, Front tickets, small perf PRs) with its outputs held for human review. Use when someone wants an agent to keep doing a kind of work on a schedule, rather than one-off. Walks the interview, runs one real item live before arming anything, then writes the playbook and creates the loop.
日本語の概要は準備中です。原文の説明を表示しています。