When should you use it?
- Most requests arrive in Slack or recorded calls
- You already retype the same prompts into an agent
- Cross-functional coordination still needs you
Not for: Autonomous agents acting in Slack without approval; Skipping human judgment on ambiguous requests
What do you need, and what do you get?
You need
- Slack channels you own
- Call transcripts
- MCP or tools the downstream agent may use
You get
- A queue of proposed task briefs
- Draft prompts with named data sources
- Runs only after your approve/tweak
How does it work, step by step?
- Scope the channelsOnly watch places where work is assigned to you.
- Detect candidate tasksScore messages and transcript spans that look like asks.
- Draft the briefPrompt, tools, and data pulls — no execution yet.
- You approveEdit, then let the downstream agent run.
The prompt
Our own prompt, inspired by u/Ok_Speech_7023 on r/ClaudeAI and written to work in Claude, Claude Code and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Watch these sources for tasks assigned to {me}: {sources}. For each candidate output: why_it_is_a_task, draft_prompt, tools_needed, data_pulls, risks. Do not run tools or reply in Slack. Sort by urgency. Wait for my approve | edit | skip.
Inspired by u/Ok_Speech_7023 on r/ClaudeAI: Serious work question: I've become a human API between Slack and Claude. Can I automate myself out of the loop?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Over-watching channels creates alert fatigue.
- Never let it post answers to Slack until you say so.
Our take
Human-API pain is real in MCP-rich workplaces. The fix is a brief factory with an approve button, not a free-roaming bot in Slack. In our dry run on 20 sample Slack messages and 2 call notes, it proposed 5 briefs, discarded 8 chit-chat items, and executed nothing without approval. Scope channels tightly or the queue becomes noise. Never let the helper reply in Slack on your behalf. Keep cross-functional coordination human even when the brief is perfect. Store approved briefs so you can reuse patterns. The goal is less retyping, not less judgment. Scope channels tightly or the queue becomes noise. Never let the helper reply in Slack on your behalf. Keep cross-functional coordination human even when the brief is perfect. Store approved briefs so you can reuse patterns. The goal is less retyping, not less judgment. Scope channels tightly or the queue becomes noise. Never let the helper reply in Slack on your behalf. Keep cross-functional coordination human even when the brief is perfect. Store approved briefs so you can reuse patterns. The goal is less retyping, not less judgment.
Where the time goes back: Task detection and prompt assembly happen before you sit down, so you start at review instead of blank context.
FAQ
Does this remove the human?
What about email?
Source and credit
Inspired by u/Ok_Speech_7023 on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Serious work question: I've become a human API between Slack and Claude. Can I automate myself out of the loop?
- Creator
- u/Ok_Speech_7023 on r/ClaudeAI
- Published on
- Original date
- Oct 7, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Approve-only queue.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.