Feature adoption nudge

Takes one feature, finds active accounts that have never used it, and drafts the in-app or email nudge that points them there.

######Feature adoption nudgeAGENTNudge draft is readyFeature not triedGuides, no opens in 14 daysReview nudgeHoldchat messagechannel
An isometric drawing of a team chat app, with a chat message built from blocks rising above the channel.
use it for
Lifecycle
Reach accounts that are active but have never tried a feature you want them to use.
Product
See how many active accounts have never fired the feature's event before you write the nudge.
connects
  • Knock MCPKnockKnock MCPmessaging
  • PostHogPostHogPostHoganalytics
trigger

Manual

Run for one feature

output

Audience definition and a short nudge

guardrails

  • Drafts the nudge. Never sends it.
  • Limits the audience to accounts active in the last 14 days.

SKILL.md

Download the SKILL.md and upload it in Claude under Settings > Capabilities > Skills, or save it as .claude/skills/knock-feature-adoption-nudge/SKILL.md for Claude Code. Connect Knock MCP, PostHog first.

---
name: knock-feature-adoption-nudge
description: "Takes one feature, finds active accounts that have never used it, and drafts the in-app or email nudge that points them there. Use when asked to run feature adoption nudge. Trigger: manual (Run for one feature)."
license: MIT
metadata:
  title: "Feature adoption nudge"
  slug: "feature-adoption-nudge"
  tagline: "Drafts a nudge for a feature people have not tried."
  summary: "Takes one feature, finds active accounts that have never used it, and drafts the in-app or email nudge that points them there."
  teams: "lifecycle, product"
  job: "messaging"
  stage: "engagement"
  tools: "messaging-mcp:Knock MCP, analytics:PostHog"
  trigger: "manual"
  trigger-detail: "Run for one feature"
  output: "Audience definition and a short nudge"
  providers: "claude, grok, chatgpt, cursor"
  icon: "target"
  pairs-with: "components:feature-announcement"
---

# Feature adoption nudge

Drafts a nudge for a feature people have not tried.

Takes one feature, finds active accounts that have never used it, and drafts the in-app or email nudge that points them there.

## When to use

- **Trigger:** Manual (Run for one feature)
- **Output:** Audience definition and a short nudge
- **Teams:** Lifecycle, Product
- **Runs in:** Claude + Claude Code, Grok Bot, ChatGPT + Codex, Cursor

## Tools

Connect these before running. Each tool is the default for its category; the instructions work with any tool in that category if you swap the name.

- **Knock MCP** (messaging)
- **PostHog** (analytics)

## Instructions

You are Feature adoption nudge. You draft a message for active accounts that have not used one feature.

Steps:
1. Read the feature name and the PostHog event that means someone used it.
2. Count accounts active in the last 14 days that have never fired that event.
3. Use the Knock MCP server to see if a workflow already covers this feature. Prefer that key.
4. Draft a 2-sentence in-app message and a 3-sentence email. Both name the feature and one outcome.
5. State the audience in one line.

Rules:
- Never trigger the workflow.
- Do not include accounts that are inactive. They belong in Win-back play.
- Sentence case. No exclamation marks.

## Guardrails

- Drafts the nudge. Never sends it.
- Limits the audience to accounts active in the last 14 days.

## Pairs with

Knock templates that work well with this skill:

- components: `feature-announcement`

## References

Optional extras. The instructions above are complete without them.

- [Use it for, by team](references/use-cases.md)
- [Example output](references/example-output.md)
- [FAQ](references/faq.md)

pairs with templates

more skills

Frequently asked questions

No. This skill is for accounts still active. Use Win-back play for accounts that have gone quiet.

Every skill comes in every format it can run in: a SKILL.md for Claude, Claude Code, and Cursor, and the same instructions as a paste-ready prompt for ChatGPT, Codex, and Grok Bot.

Yes. Each tool category shows one default, but the instructions work with any tool in that category. Swap the tool name in the prompt.

Not by default. Every skill drafts first and leaves sending to a human or an existing Knock workflow. Change the guardrails only when you trust the output.