Finds the "how do I…" questions your users keep asking and drafts short walkthroughs for the few that really deserve one, ready to send by link from a support reply, a help article or your Adoption Agent.
Download
What it does
The skill reads the questions people asked your Adoption Agent, and, if you connect one or paste an export, your support tool's conversations too. It leaves out your own staff and test accounts, groups the rest by what users were trying to do, and runs every topic through a set of checks. Only topics that pass all of them become candidates.
A topic also needs real evidence that it keeps coming up:
3 or more different people asked it in the window.
At least one sign of frustration—the Agent couldn't answer, someone gave a thumbs-down or negative written feedback, asked again, or was escalated to a person.
It came up in 2 or more different weeks.
You get a short report with up to three candidates, each with the question, the click path, who it's for, and where to share it. Topics that came close go on a watch list for next time, and dropped topics are counted by reason. After you say which to draft, each one is created as an unpublished flow with a customer-facing title such as "How to export a report". Each draft also comes with a Flow purpose text to paste into your Adoption Agent, so the agent knows when to offer the flow.
What you'll need
The Userflow MCP connected, with editor access or above to create drafts
At least one source of questions: a published in-app Adoption Agent with conversations in the window, a connected support tool (such as Intercom, Zendesk, Freshdesk, HubSpot or Help Scout), or an exported CSV of support conversations
Optional: a task tool such as Asana, Jira, Linear or Trello, to track each draft until it's published
How to use it
"Users keep asking the same questions. What should be a flow?"
"Find flow candidates from our Adoption Agent."
"Turn our repeat support questions into walkthroughs."
The default window is the last 30 days. You'll be asked for your company's email domains so staff and test accounts can be left out, and, when it's time to draft, for your app's URL and the theme to use. If you kept a watch list from a previous run, share it and topics keep the same names across runs.
What makes a good candidate
A topic is dropped if any of these is true. Most repeat questions are better answered by a help article, and the report tells you how many went that way.
The answer isn't a fixed set of clicks ("it depends", "here's why that happened").
It needs the user's own content or setup to work, so a flow opened from a link couldn't help.
The steps happen outside your product, such as in email, code or another tool.
The screens are in beta, recently redesigned, or about to change.
It's longer than about six steps or spans several areas of the product.
People are asking because something is broken. That's a bug, not a flow.
Topics for a specific plan or role can still pass, labelled with who they're for.
Things worth knowing
Zero candidates is a normal result. The bar is strict on purpose. The skill won't lower it or stretch a check just to have something to show. On a small account it may offer, once, to accept topics asked by two people instead of three.
Drafts are never published, and never start on their own. They start only from a link, an Adoption Agent recommendation, a launcher or the resource center.
Preview every step in the Builder. The skill only points steps at elements it has seen in your existing flows or at exact button text. Where nothing reliable exists, it uses a speech bubble and tells you which steps to point.
The Flow purpose text is something you paste. The skill can't set that field itself. The text is written in general terms, because your Adoption Agent answers every user: it never includes customer names, emails, company names, or anything users pasted.
An existing flow can still be the answer. If users keep asking about something a published flow already covers, the skill says so and gives a Flow purpose text for that flow instead of drafting a new one.
Typed feedback counts. Negative written feedback is treated as a thumbs-down, even when the user didn't click one.
Your users stay anonymous in the report. It cites conversation IDs and paraphrases questions, never names, emails or company names.
What to do with it
Once a draft looks right, publish it. Then add it to your Adoption Agent's sources (Adoption Agent → Sources → Flows), paste the Flow purpose text into the flow's Flow purpose field, and publish the agent: a new source isn't used until the agent is published again. Link the flow from the matching support macro and help article. If you use a task tool, the skill offers one task per draft with this checklist; if none is connected, it asks which tool you use. Check views and completions after a month. Run the skill every two to four weeks so the watch list keeps up. For features nobody asks about but few people use, see userflow-create-adoption-nudges.