Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Design an email program, from a welcome series to a sales sequence or newsletter. Decide what to send, in what order, to whom and how to measure it.
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.
Each of these library teams gives its bots this skill. Import one and look inside first.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
73 lines · 761 words
Mode skill. Default-enabled on the Channels specialist.
Use when the user needs to design an email program, welcome sequence, nurture flow, sales sequence, lifecycle program, newsletter cadence, and needs structure for what to send, in what order, to whom, with what stage assignment. Use when the brief mentions email funnel, autoresponder, drip campaign, or newsletter strategy.
Trigger phrases:
Design an email program, from a welcome series to a sales sequence or newsletter. Decide what to send, in what order, to whom and how to measure it.
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 Email Sequences 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.
The principle
**Mode skill.** Default-enabled on the Channels specialist.
What it covers
When to use
Procedure
Decision rules
Anti-patterns
Before / after
"What should I email my list?"
"Design a sales sequence for…"
"How often should I send newsletters?"
If Copy has voice constraints in TEAM_MEMORY.md, read them before specifying structure.
1. Assign the sequence a stage. Each sequence has one job; do not mix.
Consideration-stage welcome sequence: the new subscriber knows the problem and is evaluating you. Goal: build authority and trust over 4-7 emails, no hard sell.
Buying-stage sales sequence: the subscriber is warm and offer-aware. Goal: drive a single conversion event over 3-5 emails with rising urgency.
Retention-stage lifecycle: the subscriber is a customer. Goal: onboarding, retention, expansion. Triggered by behavior (purchase, milestone, inactivity).
Standing newsletter: recurring broadcast that holds the relationship. Goal: maintain mental availability between purchase decisions.
2. Design the sequence structure. For each email, specify: (a) stage role inside the sequence (introduce, deepen, prove, ask, close), (b) trigger (signup, time delay, behavior event), (c) primary CTA, (d) one objection it neutralizes. Hand the structural brief to Copy; do not draft email bodies yourself.
3. Trigger architecture.
Time-based: send-after-signup intervals (day 0, day 1, day 3, day 7) for welcome flows.
Behavior-based: triggered by site events, click history, purchase, inactivity. Stronger than time-based but requires event-tracking infrastructure (route to Lens).
Segmented broadcasts: newsletter sends filtered by interest tags or engagement recency.
4. Cadence and list hygiene. Default sustainable cadence: 1 newsletter per week + behavior-triggered sequences. Prune unengaged subscribers (no opens in 90 days) on a rolling basis, inbox-provider deliverability falls with low engagement rates.
5. Define measurement by stage. consideration-stage welcome: open rate, click rate, sequence-completion rate. buying-stage sales: conversion rate per email, sequence-revenue, unsubscribe rate (acceptable spike). retention-stage lifecycle: feature-adoption rate, time-to-second-purchase, churn-rescue rate. Newsletter: long-run open rate trend, click-through to the one weekly CTA.
One stage per sequence. A welcome flow that pitches three offers is doing two jobs and one badly. Separate the welcome flow from the sales sequence; trigger the sales sequence from the welcome flow's end.
One CTA per email. Two CTAs split attention and conversion. The body proves the case; the button delivers the click.
Subject line earns the open; first line earns the read. Spec the subject line as a separate brief item; route to Copy.
Behavior beats time when you can measure it. A sequence triggered by "viewed pricing page" out-performs a generic day-7 send.
Unsubscribe is a feature, not a bug. A growing list with 15% open rate is worse than a smaller list at 35%. Let people leave; protect deliverability.
Sending every subscriber every email. Segmentation by signup source and engagement recency lifts every metric.
Stacking offers into the welcome sequence. New subscribers have not earned the right to be sold to; the welcome flow earns it for them.
Treating "more sends" as the growth lever. List quality and segmentation precision beat raw send volume.
Letting the sequence run forever. Every sequence has an end state; design the exit (handoff to newsletter, re-engagement branch, or sunset tag).
Quoting benchmark open rates as targets. Industry averages span 5× variance by sender reputation; build your baseline.
Brief: "Build me an email funnel."
Before (no stage map, mixed jobs):
7-email sequence: welcome, story, pitch, social proof, urgency, last call, follow-up.
After (stage-separated, sequence-architected):
Two sequences, not one. (1) consideration-stage welcome flow, 4 emails over 7 days: introduce the problem framing, share one customer story (no offer), deliver one useful framework, invite to a low-commitment next step. Exits to newsletter. (2) buying-stage sales sequence, triggered by [behavior event], 4 emails over 5 days: offer reveal + objection 1, proof + objection 2, scarcity setup, last-call. One CTA per email. Route subject lines and bodies to Copy with stage tags. Lens spec the event tracking.
SKILL.md
73 lines · 761 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
Email Sequences bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for