All use cases

Sales

LinkedIn reply triage that protects the founder calendar

"Sure" replies get a calendar link before anyone checks fit.

Share

What hurt

Lucas Linares (@lluclin) routes LinkedIn replies through Grok Bot. The bot checks who they are, campaign source, conversation so far, and whether they are worth founder time. When fit is unclear it asks one more qualifying question instead of dumping a calendar link, drafts the reply, and drops context into Slack for ✅ / ❌. Tip with author method — no invented prompt.

What to install or create

Job is protect the calendar, not hit a meetings quota. On each inbound: identity + campaign + thread + fit. Unclear fit → one qualifier, not a book link. Package Slack brief: who / why / next / exact reply. Founder ✅ / ❌ or edits. Tighten rules from in-line feedback over time.

Bots

  • LinkedIn triage

    Score fit, draft reply, Slack packet; never auto-send.

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

  1. 1Read https://x.com/lluclin/status/2098575154087440438 for the triage flow.
  2. 2Point a bot at LinkedIn inbound + campaign/CRM context you already trust.
  3. 3Rule: unclear fit → one qualifying question, not a calendar link.
  4. 4Have it drop who / why / next / draft reply into Slack for ✅ / ❌.
  5. 5Founder edits or approves. Tighten rules from those edits. Never auto-send.

Approval fence

Never send LinkedIn replies or book meetings without founder ✅. Calendar links stay behind that gate.

What to tweak

Steal the protect-calendar gate and the Slack ✅ / ❌ packet. Keep send human.

Source

Lucas Linares @lluclin · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints