Update to Knock

{
  "name": "knock-setup",
  "description": "Connect Knock to your coding agent, discover and build notification workflows, and recommend how to trigger them from your application.",
  "included_files": [
    {
      "relative_path": "rules/build-workflows.md",
      "size_in_bytes": 818
    },
    {
      "relative_path": "rules/connect-claude.md",
      "size_in_bytes": 2988
    },
    {
      "relative_path": "rules/connect-codex.md",
      "size_in_bytes": 3812
    },
    {
      "relative_path": "rules/connect-cursor.md",
      "size_in_bytes": 2823
    },
    {
      "relative_path": "rules/connect-grok-bot.md",
      "size_in_bytes": 2630
    },
    {
      "relative_path": "rules/connect-knock-cli.md",
      "size_in_bytes": 2361
    },
    {
      "relative_path": "rules/discover-workflows.md",
      "size_in_bytes": 2416
    },
    {
      "relative_path": "rules/implement-data-source.md",
      "size_in_bytes": 8537
    },
    {
      "relative_path": "rules/import-users.md",
      "size_in_bytes": 5544
    },
    {
      "relative_path": "rules/recommend-implementation.md",
      "size_in_bytes": 2020
    },
    {
      "relative_path": "rules/wrap-up.md",
      "size_in_bytes": 6670
    }
  ],
  "skill_md_contents": "---\nname: knock-setup\ndescription: Connect Knock to your coding agent, discover and build notification workflows, and recommend how to trigger them from your application.\n---\n\n# Setup\n\nEnd-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.\n\nWhile 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 Codex MCP 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.\n\n## How to use this skill\n\n**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.\n\n1. **Open with encouragement, then confirm Knock account** (required first action — do this before anything else)\n   - **Opening (first message only).** Before the account ask, say a short word of encouragement (about 2–3 sentences): they are going to save a lot of time building notifications with Knock, this was a good call, and we will give it our best shot to get them set up as fast as possible. Keep it warm and plain — not a feature pitch, not a menu of next steps.\n   - **Default: always ask.** That same first message must then ask whether they have a Knock account. Do not add MCP, run OAuth, install skills, discover workflows, or call Knock tools until they answer.\n   - **Skip only if** the user's message explicitly says they started from the Knock dashboard (e.g. pasted a dashboard setup prompt, or says \"from the Knock dashboard\"). MCP already configured, a prior chat, or guessing they might have an account does **not** count — still ask. Still include the opening encouragement in that first message.\n   - If they say no: do **not** send them to the dashboard to sign up separately. Tell them in one line that they'll create their account during the sign-in step — signup, onboarding, and returning here all happen in that one browser flow — then continue to Connect Knock tooling.\n   - End the ask as the last line, bolded, e.g. **Do you already have a Knock account?**\n\n2. **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)\n   - Route by tool family, then follow the **surface check at the top of that rule** (app vs CLI) — do not pick a path from this list alone:\n     - **Cursor** (editor or Cursor CLI) → `rules/connect-cursor.md` — editor uses MCP; Cursor CLI is routed to `rules/connect-knock-cli.md`\n     - **Claude** (app or Claude Code) → `rules/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.md`\n     - **Codex** (IDE/app or Codex CLI) → `rules/connect-codex.md` — IDE/app uses MCP + new-task handoff; Codex CLI is routed to `rules/connect-knock-cli.md`\n     - **Any other terminal/CLI agent** → `rules/connect-knock-cli.md` — install the Knock CLI and auth with `knock login`\n   - If the tool is unknown, ask which one, then follow the matching rule.\n   - On the Knock CLI path, do **not** set up MCP at any point in this skill — no `claude mcp add`, no `codex mcp add`, no `mcp.json` edits, no connector ask. Use `knock` CLI equivalents wherever later steps mention Knock MCP tools.\n   - Auth proof: call `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.\n\n3. **Discover workflows** (`rules/discover-workflows.md`) — only after step 2 auth proof\n   - If this conversation already has an approved build list from `knock-lifecycle-opportunities` or `knock-product-messaging-strategy`, skip rediscovery (see prior-confirmation gate in that rule).\n   - Otherwise learn the product, propose high-value workflows, and confirm which to build.\n\n4. **Build workflows** (`rules/build-workflows.md`)\n   - Create confirmed workflows in the Knock development environment via MCP.\n\n5. **Recommend an implementation approach** (`rules/recommend-implementation.md`)\n   - Pick one trigger path, ask the user to confirm, then create branch `knock-implementation` before file changes.\n   - For a Knock Data Source (CDP or custom HTTP), follow `rules/implement-data-source.md`.\n\n6. **Wrap up** (`rules/wrap-up.md`)\n   - Always send a test. Follow the MCP path or Knock CLI path in `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.\n   - Always mention setting up in-app notifications via `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).\n\n## Extension rules (not on the first pass)\n\nUse these when preparing for production or when the user asks — they are optional after the main flow:\n\n- **Import users** (`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.\n\n## Rule files reference\n\n- `rules/connect-cursor.md` — Cursor: surface check, then editor MCP + skills install (Cursor CLI routes to `connect-knock-cli.md`)\n- `rules/connect-claude.md` — Claude: surface check, then app directory connector (Claude Code routes to `connect-knock-cli.md`)\n- `rules/connect-codex.md` — Codex: surface check, then IDE/app MCP + new-task handoff (Codex CLI routes to `connect-knock-cli.md`)\n- `rules/connect-grok-bot.md` — Grok Bot escape hatch: intro, MCP connect, then route\n- `rules/connect-knock-cli.md` — shared Knock CLI path: install + `knock login` auth for CLI-based tools\n- `rules/discover-workflows.md` — Product discovery and workflow proposals\n- `rules/build-workflows.md` — Build confirmed workflows with Knock MCP\n- `rules/recommend-implementation.md` — Choose a trigger path, confirm, branch, then implement\n- `rules/implement-data-source.md` — Source setup: identify user, mappings, MCP prompts, testing\n- `rules/wrap-up.md` — Test send (separate MCP vs Knock CLI paths) + next steps, dashboard link, and Knock agent help\n- `rules/import-users.md` — Extension: bulk-identify users for production readiness\n\n## Quick reference\n\n- MCP server URL: `https://mcp.knock.app/mcp`\n- Knock CLI: install with `npm install -g @knocklabs/cli`, auth with `knock login` ([docs](https://docs.knock.app/cli/overview))\n- Install open-source skills: `npx skills add knocklabs/skills`\n- Prefer Knock MCP tools (or Knock CLI commands on the CLI path) for workflow, step, and template creation after tooling is connected\n"
}