Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Moving existing messaging to Knock v1.0.0

Use this resource to inventory your existing notifications and plan their move to Knock

New

  • 455 downloads
  • 238 likes
  • 203 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install migrate-messaging-to-knock

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent scans the code for notification sends, maps each one to Knock concepts and writes an ordered migration plan. It creates or changes no Knock resource unless you approve the plan after reviewing it.

Mostly picked by

Updated November 2, 2026

Card for the “Moving existing messaging to Knock” skill

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • rules/inventory-existing-messaging.md: inventory of messaging in the code
  • rules/map-concepts-to-knock.md: mapping to Knock concepts
  • rules/migration-plan.md: ordered migration plan

Good fit for

  • You are leaving Braze, Courier, Customer.io or SendGrid for Knock
  • You want to estimate the effort of a migration before starting it

Not for

    Tags

    • migration
    • notifications
    • knock
    • inventory

    About

    You say

    “Inventory the notifications in my app and propose a migration plan to Knock.”

    Card for the “Moving existing messaging to Knock” skill

    Skill published by knocklabs under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to inventory your existing notifications and plan their move to Knock
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • rules/inventory-existing-messaging.md2.4 KB
    • rules/map-concepts-to-knock.md4.3 KB
    • rules/migration-plan.md3 KB
    • SKILL.md4.1 KB

    Origin and licence

    Listed unmodified

    Author
    knocklabs
    Source
    github.com/knocklabs/skills/tree/48512cc72a41e27ecea403fcf48bf1a09ceff87a/skills/knock-migrate-to-knock
    Licence
    MIT

    Notice

    « knock-migrate-to-knock » (knocklabs, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.