Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Collect your customers' own words from reviews, calls and replies, and use them in headlines and copy.
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
81 lines · 765 words
Mode skill. Default-enabled on the Copy specialist.
Use any time you are about to write a headline, hero, CTA, email body, ad, landing section, or rewrite. Use before drafting, not after. If a teammate hands you a brief without customer voice, run this mode first and report back.
Trigger phrases that should activate this mode:
"Write me a headline for…"
Collect your customers' own words from reviews, calls and replies, and use them in headlines and copy.
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 Customer Voice 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 Copy specialist.
What it covers
When to use
Procedure
Decision rules
Anti-patterns
Before / after
Each of these library teams gives its bots this skill. Import one and look inside first.
"Draft an email for…"
"Improve this landing page…"
"What should the CTA say?"
If voice has already been mined (Research has posted quotes to TEAM_MEMORY.md, or the user dropped reviews in chat), skip to step 3.
1. Source the voice. Ask the user for one of the following, in order of preference:
Recent customer reviews (any platform, raw text — not summaries).
Support tickets or refund requests (exact wording).
Sales-call transcripts or recorded discovery calls.
DMs, comment threads, community posts from the target audience.
User-interview notes with verbatim quotes.
If the user has nothing, ask one question: "Can you tell me one sentence a real customer has said about why they bought (or almost did not buy)?" That one sentence is the seed.
2. Extract verbatim. Read the source material. Pull exact phrases — not paraphrases. Tag each pull with the emotion or job it expresses:
Pain phrases. What the reader feels before the product exists. ("I was drowning in tabs.")
Outcome phrases. What they got. ("I finally took a Friday off.")
Hesitation phrases. Why they almost did not buy. ("I thought it would be one more thing to manage.")
Trigger phrases. What pushed them over the line. ("I tried it on a Sunday night because I could not face Monday.")
Aim for 5–15 pulls. More if the source is long. Group them in TEAM_MEMORY.md under ## Copy / Customer Voice so teammates can reuse them.
3. Decide: ship raw or translate. Two cases.
Ship raw when the customer phrase is already concrete, specific, and stage-appropriate. Customers describe their own pain better than you can. ("I was drowning in tabs" beats any rewrite.) Use the phrase verbatim in the headline, hook, or hero subline.
Translate when the phrase is too narrow (one customer's idiom), too long, or wrong-stage (e.g., a product-aware phrase used in an unaware-audience asset). Keep the structure and emotional register; tighten the wording. Never rewrite into corporate voice — that is the failure mode this mode prevents.
4. Cross-check against Brand. If Brand has posted voice constraints in TEAM_MEMORY.md, run the chosen phrase past those constraints. If a verbatim phrase violates a banned-word rule, surface the tension to the user rather than silently rewriting.
Verbatim wins on landing pages and ad headlines. That is where stage-1 conversion is most fragile and customer-language lift is largest.
Translate for cold email subject lines. Verbatim customer language often runs too long for 50-character inbox display. Keep the emotional core, cut the words.
Never combine pulls from different stages. A product-aware testimonial dropped into an unaware-audience ad reads as noise. Match the stage of the source to the stage of the asset.
When voice and your taste disagree, voice wins. This is the rule under all the others.
Writing copy from your head, then "checking" against voice later. The order matters — voice first, draft second.
Paraphrasing reviews into smoother prose. The bumps are the point. Customer language is bumpy.
Treating one customer's phrase as universal. Pull patterns across multiple sources before locking a phrase as the headline.
Mining only positive reviews. Hesitation and refund language is more valuable for objection-handling copy than glowing testimonials.
Inventing customer voice when none exists. If the user has nothing, do not draft — surface the gap and route to Research for a 30-minute mining task.
Brief: "Write a headline for our project-management app. Audience: solo founders."
Before (written from your head):
Streamline your workflow. Built for ambitious founders.
After (using a verbatim pull from three founder interviews):
Stop ending every Friday with the same six tabs open.
The pain phrase did the work. Three founders said versions of "I keep the same six tabs open all week" in interviews. The verbatim phrase is more specific than any synonym you would have written, and it lands inside the reader's head — not next to it.
SKILL.md
81 lines · 765 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
Customer Voice bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for