Terminal
Terminal/Skill
Plans how a product's messages across channels drive activation and retention while limiting notification fatigue.
By Knock
Works with
npx skills add knocklabs/skills --skill knock-product-messaging-strategyTurn a product into a coordinated messaging system — not a pile of one-off notifications. This skill operationalizes The product leader's guide to effective messaging into agent steps that produce Knock-ready plans and resources.
Complementary manuals:
Write the full plan to knock-plan.md (repo root). Keep chat minimal — status + confirmation only. Follow rules/knock-plan-file.md.
Do not paste full recommendation briefs, taxonomies, or checklists into chat. Rely on the plan file as the source of truth for context and for handoff to knock-setup.
Work through these rule files in order when designing or auditing a messaging system. Put detailed findings in knock-plan.md as you go; do not narrate them in chat.
rules/data-foundation-and-triggers.md to list meaningful moments and required event data — write them into knock-plan.md.rules/measurement-and-review.md before marking build-ready in the plan.rules/apply-in-knock.md to enrich Knock shapes in the plan (or create resources only if the user explicitly asks). Prefer Knock MCP / CLI when connected.knock-plan.md, then ask which items to build. Confirmation question last, bolded.knock-plan.md (Audit section).rules/measurement-and-review.md.knock-setup.knock-notification-best-practices.knock-in-app-ui.knock-cli.When handing off to knock-setup, update Setup handoff in knock-plan.md and pass the same lists in chat (no re-ranking unless the user asks):
### Setup handoff
- **plan.** knock-plan.md
- **confirmed.** [names or indexes]
- **skipped.** [names or indexes]
- **deferred / blocked.** [names + reason]
knock-setup must treat confirmed as authoritative, read detail from knock-plan.md, and skip rediscovery.
rules/knock-plan-file.md — plan file path, structure, and chat brevity rulesrules/data-foundation-and-triggers.md — events, payloads, and moment typesrules/recipients-and-ownership.md — recipient selection and escalationrules/delivery-strategy.md — channel progression and timingrules/volume-and-batching.md — frequency, cooldowns, digestsrules/relevance-and-preferences.md — context, personalization, prefsrules/measurement-and-review.md — outcomes, fatigue, launch standardrules/apply-in-knock.md — map decisions onto Knock primitives