Terminal
Terminal/Skill
Connect Knock to your coding agent, discover and build notification workflows, and recommend how to trigger them from your application.
By Knock
Works with
npx skills add knocklabs/skills --skill knock-setupEnd-to-end Knock setup for a coding agent: connect tooling, design and build notification workflows, then wire them into the application. Work through the rules below in order.
While working, keep every response to one short line — no summaries, no menus, no extra questions unless a step fails. The only exceptions are the opening encouragement + account ask (step 1), the workflow proposals, a prior-confirmation restatement (2–3 lines max), the implementation confirmation ask, the import-users id ask, the wrap-up signup-email ask (only when whoami has no email), the final wrap-up output, the ChatGPT and Codex in-app plugin surfacing, Codex CLI /plugins path, and new-session handoff in rules/connect-codex.md, and the Claude connector instructions in rules/connect-claude.md (directory link + connected ask), which have their own formats. When you end with a confirmation question (account, workflows, implementation, import-users id, wrap-up signup email, or wrap-up guides ask), that question must be the very last line of the message, on its own, and bolded.
Grok Bot: if this is Grok Bot (desktop/iOS teammate, Agent Computer, or /workspace), stop here and follow rules/connect-grok-bot.md instead of the steps below.
Open with encouragement, then confirm Knock account (required first action — do this before anything else)
rules/connect-codex.md. Plugin sign-in covers signup. The Codex IDE extension is unsupported — that rule will stop.Connect Knock tooling for the current tool (hard gate — do not discover, propose, or build workflows until a Knock MCP tool call, or knock whoami on the CLI path, has succeeded)
rules/connect-cursor.md — editor uses MCP; Cursor CLI is routed to rules/connect-knock-cli.mdrules/connect-claude.md — app adds Knock from the connectors directory (give the user the directory link and wait); Claude Code is routed to rules/connect-knock-cli.mdrules/connect-codex.md — identify the host interface (in-app, Codex CLI, or IDE extension). Do not use shell access to decide. In-app and Codex CLI use the Knock plugin; the IDE extension stops. Do not install skills separately.rules/connect-knock-cli.md — install the Knock CLI and auth with knock loginclaude mcp add, no codex mcp add, no mcp.json edits, no connector ask. Use knock CLI equivalents wherever later steps mention Knock MCP tools.list_environments or execute_mapi_read GET /v1/whoami (MCP), or run knock whoami (CLI), and wait for success. Checking that MCP or the CLI is installed is not enough.Discover workflows (rules/discover-workflows.md) — only after step 2 auth proof
knock-lifecycle-opportunities or knock-product-messaging-strategy, skip rediscovery (see prior-confirmation gate in that rule).Build workflows (rules/build-workflows.md)
Recommend an implementation approach (rules/recommend-implementation.md)
knock-implementation before file changes.rules/implement-data-source.md.Wrap up (rules/wrap-up.md)
rules/wrap-up.md (do not mix). Shared recipient rules: whoami email + name, or ask for signup email only if missing. Then next steps, dashboard link, and close with Knock agent help.knock-in-app-ui. If guides were created or mentioned, note that guides need app wiring — then ask before starting knock-in-app-ui (do not proceed until the user says yes).Use these when preparing for production or when the user asks — they are optional after the main flow:
rules/import-users.md) — choose a stable Knock user id, research how users are stored, set KNOCK_API_KEY, and write a dry-run-first bulk-identify script. Do not run against production unless the user explicitly asks.rules/connect-cursor.md — Cursor: surface check, then editor MCP + skills install (Cursor CLI routes to connect-knock-cli.md)rules/connect-claude.md — Claude: surface check, then app directory connector (Claude Code routes to connect-knock-cli.md)rules/connect-codex.md — ChatGPT and Codex: host-interface surface check, then in-app plugin or Codex CLI /pluginsrules/connect-grok-bot.md — Grok Bot escape hatch: intro, MCP connect, then routerules/connect-knock-cli.md — shared Knock CLI path: install + knock login auth for CLI-based toolsrules/discover-workflows.md — Product discovery and workflow proposalsrules/build-workflows.md — Build confirmed workflows with Knock MCPrules/recommend-implementation.md — Choose a trigger path, confirm, branch, then implementrules/implement-data-source.md — Source setup: identify user, mappings, MCP prompts, testingrules/wrap-up.md — Test send (separate MCP vs Knock CLI paths) + next steps, dashboard link, and Knock agent helprules/import-users.md — Extension: bulk-identify users for production readinesshttps://mcp.knock.app/mcpnpm install -g @knocklabs/cli, auth with knock login (docs)npx skills add knocklabs/skills