Finds the features your customers are missing out on and drafts a gentle in-app nudge for the accounts most likely to try them: the ones already doing something closely related.
Download
What it does
You name the features you want more people to use. The skill measures how many active accounts use each one, from your own event data, and finds the lookalikes: accounts that did a related thing in the last 30 days but have never used the feature. That's the group a nudge is most likely to move.
Each feature gets a score from the number of lookalikes, how much the feature matters to you, whether there's already in-app content about it, and whether people ask your Adoption Agent about it. You see a ranking table and a proposed top three, and pick which to draft. For each pick you get:
A nudge—a small speech bubble with a "Show me how" button, shown once to lookalikes and never straight after another flow.
A walkthrough for the button to start. An existing one is reused; if there isn't one, it's drafted from your help article for that feature.
A funnel chart that tracks saw the nudge → started the walkthrough → used the feature.
What you'll need
The Userflow MCP connected, with editor access or above to create drafts and charts
Events tracked in Userflow for the features you care about, plus one that means "using the product"
A help article for any feature that doesn't have a walkthrough yet
Optional: a published in-app Adoption Agent, so features people struggle with rank higher
Optional: a task tool such as Asana, Jira, Linear or Trello, to track each pick until it's published
How to use it
"Which of our features are under-used?"
"Get more users to try scheduled reports."
"Where are our adoption gaps?"
You'll be asked which event proves each feature is really used, a related behavior to find lookalikes, how much each feature matters (1 to 3), whether to count by company or by user, and who to leave out, such as your own staff, trials or a plan that doesn't include the feature. If you're not sure which features to pick, the skill suggests some from your events.
Things worth knowing
A feature needs a tracked event. If there's no event that proves someone used it, or the event has never been sent in this environment, the feature is left out and you're told why. Userflow's own events (flows, checklists, announcements and the like) never count as features.
Nothing is published. Publish the walkthrough before or together with the nudge, or its button has nothing to start.
Use the funnel, not the completion rate. The nudge has no goal step, so its completion rate stays at 0% however well it works. Funnel results are read in Userflow; the skill gives you the chart link.
Limiting a nudge to certain pages is done in the Builder. The skill gives you the exact step to add.
Small numbers are rough. Under about 30 active accounts, the percentages are flagged as rough. A feature with no users in 90 days is marked "check tracking", since the event may have been renamed.
What to do with it
Preview the walkthrough, publish it, then publish the nudge. If you use a task tool, the skill offers one task per pick with this checklist; if none is connected, it asks which tool you use. After 30 days, check the funnel. After 60 days, compare accounts that saw the nudge with similar accounts that didn't. That comparison, not the funnel alone, tells you whether it worked. For questions users actively ask, see userflow-create-reactive-flows.