In short:
ak-onboarding-croreviews your post-signup flow, settles on one activation action that predicts retention, then gives you a prioritized list of changes. Each change is based on the numbers you provide and comes with a metric to measure it. Signup forms and campaign emails go to a suitable skill you have installed. It does not send messages and does not change your product in production.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when users sign up and leave before they see the product is useful, when you do not know which action really counts as activation, or when you need to bring back users stuck at a setup step. You do not need it for signup forms or campaign emails: those belong to other skills.
flowchart LR
A["Post-signup flow + funnel numbers"] --> B["ak-onboarding-cro"]
B --> C["Prioritized changes, each with a metric"]
C --> D["Product team builds, measures by the recorded metric"]
B --> E["Signup form, campaign email: suitable installed skill"]The four things it always settles:
| Point | Question | Example |
|---|---|---|
| Activation event | Which action makes a user most likely to stay? | Creating the first project and inviting a teammate, not "finished the tour" |
| Biggest drop-off | In the funnel you provide, at which step do most users drop off? | The funnel falls hardest from completing the profile to creating a project, so the first proposal targets that step |
| Required steps | Which steps must stay even though they slow users down? | Email verification and accepting the terms stay, just moved to the moment they are really needed |
| Metric and guardrail | What shows the change works, and what shows it did not break something else? | Metric: activation rate within the time window you choose. Guardrail: support tickets do not rise |
Without retention data, activation is clearly marked as a hypothesis, along with the events you need to add to test it. It does not make up activation rates, industry benchmarks or expected lifts.
Sample prompt when you already have a flow and funnel numbers:
/ak-onboarding-cro <onboarding flow URL of your app>
Product: <product type>, sold to businesses.
Funnel for the last 30 days: signup 100%, profile completed 71%, first project created 38%, teammate invited 22%.
Common complaints: <paste a few pieces of user feedback>.
Constraints: keep the email verification step. Measure activation within the first 7 days.
Done when: there is a prioritized list of changes, each with a metric and a guardrail.This skill has no flags. After the command, write the URL of your onboarding flow or describe the flow in words. You still need to state your funnel numbers, user complaints and constraints in the request.
Below is the detailed version: the run flow, 5 situations with prompts (auditing a flow with numbers, defining activation, designing the first-run experience, bringing back stuck users, an experiment roadmap), how to write the argument, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-onboarding-cro: fix onboarding so new users activate sooner" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-onboarding-cro". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-onboarding-cro
