Terminal
Terminal/Skill
Investigates a codebase's existing messaging setup, such as Braze, Courier or SendGrid, and recommends how it maps to Knock.
By Knock
Works with
npx skills add knocklabs/skills --skill knock-migrate-to-knockDiscover the current messaging stack in this codebase, map it to Knock concepts, and produce an ordered migration plan. This is a discovery and recommendation skill.
Do not create, update, push, commit, or delete Knock resources (workflows, guides, users, tenants, preferences, partials, layouts) via MCP or CLI unless the user explicitly asks after reviewing the plan. Do not run production imports. Output plans, inventories, and optional local app-code suggestions only.
Write the inventory and migration plan to knock-plan.md at the repo root (the shared plan file used by knock-product-messaging-strategy and knock-lifecycle-opportunities; create or update — do not create a second plan). Keep chat minimal — status + confirmation only.
Do not paste the inventory table or the full phased plan into chat.
Allowed chat content:
Example:
Wrote knock-plan.md: Courier + SendGrid detected, 14 message types inventoried, 8-phase plan drafted.
Which migration phase should we plan in more detail next?
Always ground recommendations in Knock docs. Prefer these:
| Situation | Doc |
|---|---|
| Braze → Knock | https://docs.knock.app/tutorials/migrate-from-braze |
| Courier → Knock | https://docs.knock.app/tutorials/migrate-from-courier |
| Email templates via MCP (only if user asks to execute) | https://docs.knock.app/tutorials/migrate-email-with-mcp-server |
| Workflows | https://docs.knock.app/concepts/workflows |
| Channels | https://docs.knock.app/concepts/channels |
| Users | https://docs.knock.app/concepts/users |
| Preferences | https://docs.knock.app/preferences/overview |
| Tenants / multi-tenancy | https://docs.knock.app/multi-tenancy/overview |
| Subscriptions | https://docs.knock.app/concepts/subscriptions |
| Translations | https://docs.knock.app/template-editor/translations |
| Triggering workflows | https://docs.knock.app/send-notifications/triggering-workflows |
| Sources (CDP) | https://docs.knock.app/integrations/sources/overview |
rules/inventory-existing-messaging.md)rules/map-concepts-to-knock.md)rules/migration-plan.md)knock-plan.md, not chat.rules/map-concepts-to-knock.md.knock-plan.md. In chat, ask which phase to plan or execute next — do not execute Knock writes unless asked.rules/inventory-existing-messaging.md — what to find in the codebaserules/map-concepts-to-knock.md — platform concepts → Knockrules/migration-plan.md — phased plan output formatRecommended resource migration order (from Knock Braze / Courier tutorials):