Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Review the steps from signup to a customer's first useful result.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
79 lines · 861 words
You're designing what happens between signup and "this is working." Load when someone asks "how do we onboard," "what's the activation path," "why are signups dropping off," or "what do we send on day 1, 7, 30." Not for ticket replies (ticket-triage.md), not for the customer who went quiet (churn-prevention.md).
Review the steps from signup to a customer's first useful result.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Onboarding flow skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
What it covers
When to load this mode
What onboarding is for
Define the activation path
The first 30 days — three checkpoints
Decision rules
Anti-patterns
Before / after
Each of these library teams gives its bots this skill. Import one and look inside first.
The first 30 days decides retention, even when the cancel email arrives months later. A customer who didn't reach first outcome in week 1 quietly loses faith.
Before you write a single email or tooltip, write down two things.
The Required Outcome. What specific in-product result means the customer got what they bought? "Imported contacts and sent the first campaign" — not "explored the dashboard." "Connected the bank account and received the first reconciled report" — not "completed setup." A verb in the customer's world.
The Appropriate Experience. How does this segment need to get there? A self-serve indie wants no human contact, 10-minute path. Mid-market wants a 30-minute kickoff and Slack access. Enterprise wants a named contact, security review, six-week plan. Same Required Outcome with the wrong Experience still churns.
Write both. Two segments with different Required Outcomes get two paths.
Not 30 emails. Three checkpoints, each tied to an outcome milestone.
Day 0–3 — first signal the product can do the thing. One piece of evidence it behaves as hoped. Reporting tool: first real report rendered. Payment processor: first test transaction succeeded. Not a tour; one observed result. If not reached in 72 hours, intervene — not "checking in" but a message naming what's stuck.
Day 4–14 — first habitual use. Used the product more than once for the same task, in a workflow they'd repeat. Not "logged in three times" but "ran the export, edited it, ran it again." The product lives in their week.
Day 15–30 — first Required Outcome at scale. Used for the real thing — sent the campaign, closed the books, shipped the report, billed the client. Renewal is decided here, not at month 11.
Every customer-facing message in the first 30 days serves one of these checkpoints. If it doesn't, cut it.
Measure progress, don't assume it. "Days since signup" isn't progress. "Reached checkpoint 1" is. Watch each checkpoint event weekly.
One intervention per stuck checkpoint. If 25% miss checkpoint 1 in 72 hours, the message is specific to that checkpoint, not a generic "how are things?"
Don't add a kickoff call to a self-serve segment. White-glove on a speed-buyer is friction. Self-serve on a white-glove buyer is abandonment.
Route bugs blocking checkpoints as P1. A defect blocking a new customer costs more than one blocking a tenured one — they haven't earned trust yet.
Hand a clean checkpoint-3 hit to Sales. Expansion-ready signal worth routing.
Feature-tour onboarding. "Welcome! Here's the dashboard." Customer bought an outcome, not a tour.
Checklist gamification with no outcome behind it. "Complete your profile to earn 10 points!" Activity theatre.
Generic drip emails on a calendar. Day-1/3/7 emails ignoring where the customer actually is. A checkpoint-2 customer reading "have you tried logging in?" loses respect.
Trial-counter pressure with no outcome guidance. "5 days left!" with no signal about path is harassment.
Hiding the friction. If checkpoint 1 runs through three screens 40% bounce on, fix the screens, not the reminder cadence.
Before (feature-tour onboarding):
Day 1: "Welcome! Here's a tour of the dashboard." Day 3: "Have you tried our reporting feature?" Day 7: "Your trial ends in 7 days!"
40% never run a real report. Month-3 retention 22%.
After (Desired-Outcome onboarding):
Required Outcome: imports contacts and sends the first real campaign. Day 0: import flow + sample data + "send a test to yourself" prompt. Day 2 (only if no import): "Contact import hasn't completed — is the file format the blocker? Here's the common fix." Day 7 (only if no first send): "Imported but haven't sent. Want a 15-minute walkthrough, or is something specific blocking?" Day 14: review with customer — outcome reached or not, what got in the way.
Same product, same team. Activation 71%, month-3 retention 54%.
SKILL.md
79 lines · 861 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Onboarding flow bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for