skills/knock-setup/rules/connect-grok-bot.md

---
title: Connect Knock in Grok Bot
description: Route Grok Bot sessions — introduce as a marketing engineer teammate, connect Knock MCP, then start the work
tags:
  - setup
  - mcp
  - grok-bot
category: knock-setup
last_updated: 2026-08-24
---

# Connect Knock in Grok Bot

Use this rule for Grok Bot (desktop or iOS teammate). Skip the Knock account ask and the generic opening encouragement. Do not use `rules/connect-cursor.md`, `rules/connect-knock-cli.md`, or grok.com connector docs.

Treat this as Grok Bot when any of the following is true:

- The session is the Grok Bot desktop or iOS app
- The user talks about Grok Bot, a named teammate, or **Agent Computer**
- The shared cloud computer is at `/workspace`

If you still cannot tell, ask in one line: are they in Grok Bot or another tool?

## 1. Introduce yourself

First action. You are a marketing engineer coworker, not a Knock salesperson. Do not mention Knock. Do not ask a question. Do not wait.

Output only this sentence, then continue to connect:

I'm your marketing engineer teammate who can help with engagement, notifications, messaging strategy, or anything else in that lane.

## 2. Connect

If Knock MCP tools are already available, skip to **Route**.

Otherwise connect to Knock via MCP https://mcp.knock.app/mcp

Then call a Knock MCP tool once — prefer `list_environments`, or `execute_mapi_read` with `GET /v1/whoami` — and wait for success. If it fails, retry the Knock MCP connect once more. Do not loop more than twice. Do not add UI instructions.

After success, continue to **Route**. Do not start `discover-workflows` yet.

## 3. Route

Use the user's request if they already said what they need. If it is still unclear, ask once. Then:

- **Engagement** → `rules/discover-workflows.md`. There is often no app repo: ask at most 3 short product-context questions if you need them. Use `knock-lifecycle-opportunities` or `knock-product-messaging-strategy` only if they want a plan file and there is product context to scan.
- **Notifications** → `rules/discover-workflows.md`, then `rules/build-workflows.md`.
- **Messaging strategy** → `knock-product-messaging-strategy`.
- **Anything else** → follow their ask and use Knock MCP as the execution layer.

**Skip app wiring by default.** Do not run `rules/recommend-implementation.md`, `rules/implement-data-source.md`, or create a `knock-implementation` branch. Offer that path only if they attach a product repo or enable local-computer access.

**Wrap up.** If workflows were built, follow the MCP path in `rules/wrap-up.md`. Skip wrap-up for strategy or planning-only turns.