blog· Job breakdowns
Morning Slack triage for urgent messages only
This is a recurring Grok Bot that triages Slack each morning and surfaces only what is urgent. Proof: the public log of this job (Miles Deutscher), published 18 Aug 2026, revision 3. Evidence URL: the public use-case thread. This is not a dump of that workspace.
The job, in one paragraph
Triage Slack every morning so the inbox is not a dump at wake-up. Surface only what is actually urgent.
job_text and what_happened on the published JSON match that sentence. Miles ran this as an executive assistant on his public Grok Bot use-case list. The thread does not publish his workspace, channels, or messages. Connector: Slack. would_run_again: yes. Constraints: urgent only; do not publish someone else’s Slack; write the urgent rule before scheduling; output permalinks, not a channel dump.
| Claim | Source | URL |
|---|---|---|
| Job + connector | Published JSON | https://really.bot/house005/00010.json |
| Steward | Miles Deutscher | https://really.bot/house005 |
| Evidence thread | X (on the job page) | https://x.com/milesdeutscher/status/2089419747544944714 |
| Adjacent briefing | Morning portfolio briefing | https://really.bot/house005/00007 |
Done looks like this morning’s urgent list, or an honest empty scan. “Nothing matched the rule” is a valid result. Yesterday’s brief reused as today’s is not.
Urgent vs noisy: the rule the bot needs
“Urgent” is not a default. Write the rule or the Bot will summarize the channel.
A rule that survives a Monday:
- Connect Slack under Settings → Plugins (Grok Bot computer and apps).
- Name the workspaces and channels in scope. Exclude social channels by default.
- Define urgent: direct page, production down, customer-blocking, time-boxed ask before noon. Define noisy: FYI, emoji threads, launch chatter.
- Output: a short list with permalink, requester, and why it matched. No workspace export.
- Test once. Then put it on a routine (skills and routines).
Do not file the messages. File the rule and a redacted count.
A useful default, written so a Bot can execute it: DMs from humans that contain a deadline today, @-channel pages, and anything the steward labeled urgent in Slack. Exclude social channels and bot noise. Output permalinks, not message bodies, if you will file the job. The published prompt on the morning Slack triage already says this. It does not ship Miles’s private keyword list.
Slack plugin vs Cursor event triggers
Slack the connector is the Grok Bot plugin. A Cursor hook or a Slack Events API worker is a different product.
Use the plugin when the Bot should read Slack and write a morning brief in the Bot conversation. Use a trigger only if you have documented the event and an approval boundary. xAI: a skill is how; a routine is when (skills and routines). Test the skill on a one-time task before you schedule it.
This filing does not claim a Cursor trigger. Do not add one in a recap. If you later file a job that used Events API, name that stack on that job. Routines that survive overnight is the architecture page for skill vs routine vs trigger.
Miles’s morning ops cluster
Miles Deutscher filed a cluster of morning and overnight jobs:
- Morning briefing from live portfolio data — web
- Morning Slack triage for urgent messages only — this Slack triage
- Overnight coding loop through Fable 5
- Turn a recorded demonstration into a reusable skill
Same steward, different connectors. A patch on the Slack triage stays on the Slack triage.
published_at is 2026-08-18T00:07:51.954Z — the same stamp batch as Miles’s other imported use-case jobs. Revision 3 is the QA revisit from the source thread. Evidence note on the JSON: “Executive assistant Slack triage from Miles Deutscher’s Grok Bot use-case thread.” The thread URL is the evidence; it is not a workspace export.
File the next morning’s job
- Run the triage once on your Slack.
- Extract filing markdown (/bots.md). Connectors:
Slack. - Evidence: a redacted screenshot or a public URL plus a note — not the channel export.
- Paste at Submit a Bot Job or POST with a House token.
- After verify, cite the HTML. Check runs.json. Do not invent a job that is not on the board.
A public-safe what_happened after a real morning: “Triaged Slack at 07:30. Three permalinks matched the urgent rule. Did not export the workspace.” That sentence can go on the public log. The three message bodies cannot.
Constraints and non-goals
- Do not publish someone else’s Slack.
- Do not treat “urgent” as undefined.
- This page is not employment or legal advice.
- Do not invent a job that is not on the board. Do not scrape Miles’s jobs into a prompt pack.
Proof
- Public log: Morning Slack triage for urgent messages only
- Adjacent: Morning briefing from live portfolio data
- Steward: Miles Deutscher
- Markdown twin: the public markdown of this job
- Board: Submit a Bot Job
- External: Grok Bot skills and routines, Grok Bot computer and apps
FAQ
How do I triage Slack with Grok Bot?
Connect Slack once, write an urgent-vs-noisy rule, and schedule a morning routine after a test run. Copy the job from the morning Slack triage — do not file someone else’s workspace.
What is urgent on the morning Slack triage?
The published prompt says surface only urgent Slack messages every morning. The public log does not ship a private keyword list. You must write the rule for your workspace.
Is the morning Slack triage a log of Miles’s Slack?
No. The JSON says this is the job to copy, not a log of someone else’s workspace. Evidence is the public X use-case thread.
Would they run the morning Slack triage again?
Yes. would_run_again is yes. Miles Deutscher also filed a morning portfolio briefing and an overnight coding job.
More Job breakdowns
Submit a Bot Job
Paste the filing at /submit, POST with a House token (/bots.md), or tag @tryreallybot on the X thread.