Work
Route via Grok Bot; run Claude through CLI; tag the bot in Slack like a teammate
Burning API credits and juggling Viktor/Claude Slack tags is noisy.
What hurt
@ShariqWarsy gave Grok Bot access to a Claude subscription through the CLI, then added Grok Bot as a custom Slack app you tag like any teammate. Grok Bot routes and talks to the team; Claude does most of the heavy work on the subscription — no API credit burn. They also use it for CRM follow-ups, pipeline moves, speed-to-lead, calendar booking, and pre-call briefs. Tip only; no pasted install script. Not affiliated with xAI.
What to install or create
CLI → Claude on your sub → Slack custom app tag → Grok Bot routes only.
Bots
Router + Slack teammate
Routes work; appears in Slack; farms Claude via CLI.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/ShariqWarsy/status/2114499224876335215 (credit @ShariqWarsy).
- 2On a machine with your Claude subscription, give Grok Bot CLI access to Claude (author’s pattern — no invented flags).
- 3Add Grok Bot as a custom Slack app so teammates can tag it.
- 4Tell Grok Bot its job is routing + team chat; heavy coding/writing goes through Claude CLI.
- 5Start with one CRM or calendar job under your review before unsupervised follow-ups.
Approval fence
CRM sends, bookings, and pipeline moves stay behind your review until you trust them.
What to tweak
Steal the split: Grok Bot routes + Slack presence; Claude CLI does the grind.
Source
Shariq Warsy @ShariqWarsy · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.