Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Every meaningful conversation ends in one of four outcomes; only two count.
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
88 lines · 861 words
You're in sales mode and a conversation is ending — call winding down, email thread needing a reply, meeting at "so what's next." Load when someone asks "how do I close" or hands you a deal that's "going well" but has been going well for six weeks.
Every meaningful conversation ends in one of four outcomes; only two count.
Every meaningful conversation ends in one of four outcomes; only two count.
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 Close and next step 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
The distinction that organizes everything
What produces advancement
The vocabulary that produces continuation
Walk vs. push
Decision rules
Anti-patterns
Before / after
Each of these library teams gives its bots this skill. Import one and look inside first.
Order — the deal closes.
Continuation — the conversation ends without a concrete action. "Let me think about it." "Send me more info." Feels productive, produces nothing.
No-sale — the buyer says no. Underrated; a clear no frees an hour for a deal that will close.
A calendar full of "calls that went well" is usually a calendar of continuations dressed up as progress. Every conversation gets aimed at an advancement; anything else logs as continuation.
Three tests:
Concrete. A date, a name, an action. "Call with your VP of Product Tuesday 2pm" is concrete. "Sync sometime next week" is not.
Achievable. Inside the buyer's authority, doable in 7–10 days. Asking someone with no purchasing power to "get the contract signed Friday" produces a continuation.
Mutually agreed. The buyer says yes out loud. Silence is not yes. "I'll try" is closer to no.
Mechanic: where you'd say "great talk, let's stay in touch," instead say "given what we discussed, the next step would be [specific action]. Can we put that on the calendar before we hang up?" Then wait. Their answer tells you whether you have an advancement or a continuation in disguise.
Strike these:
"Let me send over some materials." Becomes a continuation almost every time.
"I'll follow up next week." With what? When?
"Take your time, no rush." Permission to do nothing.
"Just checking in." A check-in without a reason to respond is a continuation by email.
"Does that make sense?" Buyer says yes. Means nothing.
"I'll circle back."
Replace each with a concrete next step the buyer commits to.
Push when the buyer named a real problem, its cost, the value of solving it, and is hesitating on a specific addressable thing — or when internal momentum exists and the buyer is unsure of the path, not the destination.
Walk when: no advancement after multiple calls; no budget, no event, no champion; the buyer demurred on a proposed advancement twice (the third ask is pressure).
Walking isn't disappearing. Say so: "From what you're telling me, this isn't the right time. If [trigger] changes, ping me." Some come back; the rest weren't going to close anyway.
Define the target advancement before the call starts. If you don't know what it is, the call produces a continuation.
If the buyer won't commit, propose a smaller advancement before walking. From "VP intro next week" to "forward the security doc to your team this week." Won't commit to that either? Not a buyer.
Don't end a call without proposing the next step out loud. "Great chat, will send materials" is the call's continuation in writing.
"Just checking in" emails. Continuation generators. Replace with a specific question, a proposed next step with a date, or honest disengagement.
Vague follow-up cadences. "I'll touch base every couple weeks" trains the buyer they don't have to respond.
Calling the deal closed before it's signed. Hope is not commitment. A deal closes on signature, not verbal yes.
Asking for the order without earning it. "Ready to move forward?" before the buyer named the cost of inaction is a script move.
Negotiating against yourself. "I can do 10% off if that helps" is a discount the buyer didn't ask for. Don't cut your price to fill silence.
Before (continuation in costume):
Seller: "Really helpful conversation — let me send case studies and a one-pager, and I'll follow up next week." Buyer: "Sounds great, thanks."
Seller logs "good call, advancing." Three weeks of "just checking in" emails later, no reply. Deal dies.
After (advancement):
Seller: "From what we covered, the next thing is a 20-minute call with your VP of Product so I can walk her through the same numbers. Thursday or Friday?" Buyer: "Thursday 2pm should work." Seller: "Sending the invite now, with the churn numbers so she can react to specifics."
A date, a stakeholder, a defined topic. That's an advancement.
SKILL.md
88 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
Close and next step bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for