How do I install the Knock Lifecycle Opportunities skill?

Run npx skillmds@latest add knocklabs/knock-lifecycle-opportunities in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Knock Lifecycle Opportunities safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Knock Lifecycle Opportunities?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Knock Lifecycle Opportunities free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Knock Lifecycle Opportunities?

knocklabs (@knocklabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Knock Lifecycle Opportunities by knocklabs

Name: Knock Lifecycle Opportunities
Rating: 4.666666666666667 (3 reviews)
Author: knocklabs

Knock Lifecycle Opportunities

Scan a product codebase for activation, engagement, and retention moments and recommend lifecycle messaging opportunities. Use when finding onboarding, churn, trial, or habit-forming notification candidates without creating Knock resources.

knocklabs Updated Sep 9, 2026

File contents

Lifecycle opportunities skill

Find where users activate, stall, pay, invite, or churn in this product’s code and data model. Recommend messaging opportunities tied to real events and UI states.

Hard constraint

Do not create, update, push, or delete Knock resources via MCP or CLI. Output an opportunity backlog and event/trigger sketches only. Hand off to knock-setup or knock-product-messaging-strategy only if the user asks to build.

Output contract (hard)

Write all detailed findings to knock-plan.md at the repo root (create or update). Keep chat minimal — status + confirmation only.

Do not paste opportunity briefs, code-path inventories, or long rationale into chat. Follow rules/opportunity-brief-format.md.

Allowed chat content:

One short status line (path + count)
Optional one-line blocker
Bold confirmation question as the last line

Example:

Wrote knock-plan.md with 6 ranked opportunities.

Which opportunities should we take next?

Overview

Map the product lifecycle in code (rules/map-product-lifecycle.md) — write signals into the file
Select high-value opportunities (rules/select-opportunities.md) — rank in the file
Write opportunity briefs (rules/opportunity-brief-format.md) — full briefs in the file only

How to use this skill

Infer personas, accounts/workspaces, and key funnels from the repo — capture in the file, not chat.
Locate signup, onboarding, invite, billing, usage, and inactivity signals — same.
Propose at most 8 prioritized lifecycle messages in knock-plan.md.
Chat: status line + ask which to advance. Do not dump the list body in chat.
When the user asks to build in Knock or deepen strategy, hand off with a structured payload — do not invite re-ranking:

### 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. For fuller strategy design, hand off confirmed items to knock-product-messaging-strategy (same knock-plan.md).

Rule files reference

rules/map-product-lifecycle.md — where to look in code
rules/select-opportunities.md — prioritization
rules/opportunity-brief-format.md — plan file structure and chat brevity

Docs

---name: knock-lifecycle-opportunitiesdescription: Scan a product codebase for activation, engagement, and retention moments and recommend lifecycle messaging opportunities. Use when finding onboarding, churn, trial, or habit-forming notification candidates without creating Knock resources.--- # Lifecycle opportunities skill Find where users activate, stall, pay, invite, or churn in **this** product’s code and data model. Recommend messaging opportunities tied to real events and UI states. ## Hard constraint **Do not create, update, push, or delete Knock resources** via MCP or CLI. Output an opportunity backlog and event/trigger sketches only. Hand off to `knock-setup` or `knock-product-messaging-strategy` only if the user asks to build. ## Output contract (hard) Write all detailed findings to **`knock-plan.md`** at the repo root (create or update). Keep chat **minimal** — status + confirmation only. Do **not** paste opportunity briefs, code-path inventories, or long rationale into chat. Follow `rules/opportunity-brief-format.md`. Allowed chat content: 1. One short status line (path + count) 2. Optional one-line blocker 3. Bold confirmation question as the **last line** Example: Wrote `knock-plan.md` with 6 ranked opportunities. **Which opportunities should we take next?** ## Overview 1. **Map the product lifecycle in code** (`rules/map-product-lifecycle.md`) — write signals into the file 2. **Select high-value opportunities** (`rules/select-opportunities.md`) — rank in the file 3. **Write opportunity briefs** (`rules/opportunity-brief-format.md`) — full briefs in the file only ## How to use this skill 1. Infer personas, accounts/workspaces, and key funnels from the repo — capture in the file, not chat. 2. Locate signup, onboarding, invite, billing, usage, and inactivity signals — same. 3. Propose at most 8 prioritized lifecycle messages in `knock-plan.md`. 4. Chat: status line + ask which to advance. Do not dump the list body in chat. 5. When the user asks to build in Knock or deepen strategy, hand off with a structured payload — do **not** invite re-ranking: ```markdown ### 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. For fuller strategy design, hand off confirmed items to `knock-product-messaging-strategy` (same `knock-plan.md`). ## Rule files reference - `rules/map-product-lifecycle.md` — where to look in code - `rules/select-opportunities.md` — prioritization - `rules/opportunity-brief-format.md` — plan file structure and chat brevity ## Docs - https://docs.knock.app/concepts/workflows - https://docs.knock.app/concepts/guides - https://docs.knock.app/concepts/audiences - https://docs.knock.app/send-notifications/triggering-workflows/audiences - https://knock.app/manuals/product-leaders-guide-to-effective-notifications/the-product-leaders-guide-to-effective-notifications

Frequently asked questions