Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Email management mastery covering Inbox Zero methodology, filter and label systems, template libraries, batch processing workflows, unsubscribe strategies, email scheduling, follow-up tracking, and tool recommendations for reclaiming time from email.
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
429 lines · 2,116 words
Use this skill when:
User asks about email productivity techniques or best practices
User needs guidance on email productivity concepts
User wants to implement or improve their approach to email productivity
Email management mastery covering Inbox Zero methodology, filter and label systems, template libraries, batch processing workflows, unsubscribe strategies, email scheduling, follow-up tracking, and tool recommendations for reclaiming time from email.
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 Productivity 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 Use
Questions to Ask First
Inbox Zero Methodology
Filter and Label Systems
Email Templates
Batch Processing
Unsubscribe Strategy
Email Scheduling
Follow-Up Tracking
Tool Recommendations
Writing Better Emails
Common Mistakes
Process
Output Format
Edge Cases
Example
The request falls outside the scope of email productivity
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
Before overhauling your email workflow, assess the situation:
How many emails do you receive per day on average?
How much time do you currently spend on email daily?
What percentage of your email is actionable vs informational vs noise?
Do you use one email account or multiple? (Work, personal, business)
What email client do you use? (Gmail, Outlook, Apple Mail, other)
Do you currently use any email organization system? (Labels, folders, rules)
What is your biggest email pain point? (Volume, finding things, response time, anxiety)
How quickly are you expected to respond to emails? (Minutes, hours, next day)
Do you process email on mobile, desktop, or both?
Are you willing to change habits, or do you need the system to work around current behavior?
Inbox Zero is NOT about having zero emails in your inbox at all times. It's about having zero emails that haven't been decided upon. Every email has been triaged -- acted on, deferred, delegated, or deleted.
For every email in your inbox, choose ONE action:
DELETE: Not relevant, not needed -> Delete or archive
DELEGATE: Someone else should handle this -> Forward and track
RESPOND: Can be answered in 2 minutes -> Reply immediately
DEFER: Requires more than 2 minutes -> Move to action list
DO: Quick task attached -> Do it now (under 2 minutes)Step 1: The Initial Purge (One-Time)
1. Select ALL emails older than 14 days
2. Archive them all (don't delete -- archive)
- If anything was truly important, it will resurface
3. Process remaining emails (last 14 days) from oldest to newest
4. Apply the DELETE/DELEGATE/RESPOND/DEFER/DO frameworkStep 2: Ongoing Maintenance
Process email in batches, not continuously:
Morning batch (15-20 min):
Process every email using the 5-action framework
Afternoon batch (15-20 min):
Same process
Optional evening batch (10 min):
Quick scan for urgent items only
CRITICAL: Close email between batches.
Turn off notifications. Check on YOUR schedule.TOP-LEVEL LABELS (color-coded):
@ACTION (Red) - Needs a response or task from me
@WAITING (Orange) - Waiting for someone else's response
@REFERENCE (Blue) - Information I might need later
@READ (Green) - Articles, newsletters to read later
PROJECT LABELS (nested):
Projects/
Project-Alpha
Client-Smith
PEOPLE LABELS (optional, for VIPs):
People/
Boss
Key-ClientsAuto-archive newsletters:
From: contains "newsletter@" OR "noreply@"
Action: Skip inbox, apply label "@Read"Flag emails from VIPs:
From: boss@company.com, client@important.com
Action: Star, apply label "VIP", never send to spamRemove noise:
Subject: contains "Out of Office" OR "Automatic reply"
Action: Skip inbox, mark as read, archiveAutomate what's predictable: Newsletters, notifications, and automated messages always follow patterns
Never filter away actionable email: Only auto-archive informational/noise
Review filters quarterly: Remove filters for cancelled subscriptions, old projects
Start conservative: It's better to see unnecessary email than to miss important email
Use templates when you send similar messages more than 3 times per week, need consistent messaging, want to ensure key information is included, or need to respond to common inquiries quickly.
Meeting Request:
Subject: Meeting Request: [Topic] - [Duration]
Hi [Name],
I'd like to schedule a [duration] meeting to discuss [specific topic].
My availability this week:
- [Day], [Time range]
- [Day], [Time range]
Feel free to grab a slot on my calendar: [Calendly/Cal.com link]
Best, [Name]Follow-Up (No Response):
Subject: Re: [Original Subject]
Hi [Name],
Following up on my email from [date] about [topic].
[One-sentence summary of what you need from them]
Would [specific date] work for a quick response?
Thanks, [Name]Declining a Request:
Subject: Re: [Original Subject]
Hi [Name],
Thank you for thinking of me for [opportunity/request].
Unfortunately, I'm not able to take this on due to
[brief, honest reason].
[Optional: suggestion of alternative person or future timing]
Best, [Name]| Tool | Platform | Features |
|---|---|---|
| Gmail Templates | Gmail | Built-in, basic text templates |
| Text Blaze | Chrome extension | Variables, dynamic content, team sharing |
| Superhuman | Gmail | Snippets with variables and hotkeys |
| Espanso | System-wide | Open-source text expansion |
EMAIL BATCH SCHEDULE:
8:00-8:30 AM: Morning batch
- Process all overnight emails, respond to urgent items
- Defer non-urgent items to task manager
12:00-12:15 PM: Midday check
- Quick scan for urgent items only
4:00-4:30 PM: Afternoon batch
- Process all emails from the day, clear inbox
BETWEEN BATCHES: Email client CLOSED, notifications OFFTouch each email once: Make a decision immediately, don't re-read later
Two-minute rule: If it takes less than 2 minutes, do it immediately
Batch similar responses: Reply to all emails from one project at once
Use keyboard shortcuts: Saves 30+ minutes per week
Write shorter emails: Most emails should be 5 sentences or fewer
Default to "reply" not "reply all": Reduces email volume for everyone
Gmail: Outlook:
e Archive Ctrl+R Reply
# Delete Ctrl+Shift+R Reply all
r Reply Ctrl+F Forward
a Reply all Ctrl+N New email
f Forward Ctrl+Enter Send
c Compose new Delete Delete
/ Search Ctrl+Shift+V Move to folder
l Label Ctrl+Q Mark as readStep 1: Over 7 days, label every newsletter/marketing email as "AUDIT"
Step 2: For each sender, ask:
- Did I open this email? (If no 3+ times in a row: unsubscribe)
- Did I find value in it? (If no: unsubscribe)
- Does this email make me feel good or anxious? (If anxious: unsubscribe)
Step 3: Unsubscribe from everything that failed the test
Step 4: For keepers, set up filters to auto-labelOne-in-one-out rule: For every new newsletter, unsubscribe from one
Monthly audit: Spend 15 minutes unsubscribing from anything you skip regularly
Use a separate email for signups, trials, and downloads
RSS instead of email: Subscribe to blogs via RSS, not email newsletter
Time zone differences: Schedule for their morning, not yours
After-hours writing: Draft now, send during business hours
Strategic timing: Tuesday-Thursday mornings get highest open rates
Batch writing: Write all follow-ups at once, schedule across the week
| Purpose | Best Time to Send | Why |
|---|---|---|
| Business communication | Tue-Thu, 9-11 AM recipient's time | Highest open rates |
| Follow-ups | Tuesday or Thursday, 10 AM | Mid-week, mid-morning |
| Cold outreach | Tuesday 8 AM or Thursday 2 PM | Before inbox fills / afternoon lull |
| Urgent requests | Within recipient's working hours | Respect boundaries |
Most important emails that don't get a response are simply skipped by the recipient. A systematic follow-up approach dramatically improves response rates.
Send email -> Add to "Waiting For" list with expected response date
|
No response by expected date?
|-> Follow-Up #1 (3-5 business days): Reply to original thread, brief and specific
|-> Follow-Up #2 (5-7 business days later): Different angle or added urgency
|-> Follow-Up #3 / Breakup email (7 days later): "Closing the loop on this"
|-> Archive. Set reminder for future follow-up if needed.Method 1: Email Client Native -- Star/label emails when waiting, review the @Waiting label daily, remove when response received.
Method 2: Automation Tools -- Use Boomerang, Mailbutler, or Streak to auto-return emails to inbox if no reply in X days. Track open/read status optionally.
| Client | Best For | Key Feature | Cost |
|---|---|---|---|
| Gmail (web) | Most users | Search, labels, filters | Free |
| Outlook | Enterprise/Microsoft | Calendar integration | Included with M365 |
| Superhuman | Power users | AI triage, split inbox, snippets | $30/mo |
| Spark | Team email | AI compose, team features | Free-$8/mo |
| Hey | Opinionated workflow | Screening, Feed, Paper Trail | $99/yr |
| Fastmail | Privacy-focused | No ads, custom domains | $5-9/mo |
ESSENTIAL:
1. Email client with good shortcuts and search
2. Template/snippet tool for repetitive messages
3. Calendar tool with scheduling links (Calendly, Cal.com)
RECOMMENDED:
4. Follow-up automation (Boomerang, Mailbutler)
5. Unsubscribe tool (annual cleanups)Most emails should be 5 sentences or fewer:
Context (why you're writing)
Key information or request
Supporting detail (if necessary)
Clear call to action
Closing
SUBJECT LINE:
[Action Required] or [FYI] or [Decision Needed] + [specific topic]
Bad: "Quick question"
Good: "[Decision Needed] Marketing budget for Q2 campaign"
OPENING LINE:
Get to the point immediately.
Bad: "I hope this email finds you well..."
Good: "I need your approval on the Q2 marketing budget by Friday."
BODY:
Use bullet points, bold key info, one idea per paragraph.
CALL TO ACTION:
Bad: "Let me know your thoughts."
Good: "Please reply with your approval or questions by Thursday EOD."Checking email first thing: Start your day with proactive work, not reactive email
Leaving email open all day: Constant checking fragments attention and increases anxiety
Using inbox as a to-do list: Move tasks to a real task manager
Reply All by default: Ask if everyone truly needs to see your response
Long emails: If it's more than a screen of text, it should be a meeting or document
Not using templates: Rewriting the same message 10 times a week is wasted effort
Treating all emails equally: A message from your top client and a vendor newsletter should not compete for the same attention
Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
Analyze context. Review the information provided and identify key factors relevant to email productivity
Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
Present structured output. Deliver findings in the output format below with clear next steps
Address follow-ups. Answer additional questions and refine recommendations based on feedback
## Email Productivity Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Incomplete information: Ask clarifying questions before proceeding with recommendations
Conflicting requirements: Prioritize the most critical constraint and note trade-offs
Out of scope requests: Redirect to appropriate specialized skill or professional resource
Beginner vs advanced: Adjust depth and terminology based on user's experience level
Input: "Help me with email productivity for my current situation"
Output:
Based on your situation, here is a structured approach to email productivity:
Assessment: Evaluate your current state and identify key areas for improvement
Strategy: Develop a targeted plan based on best practices
Implementation: Execute the plan with specific, measurable steps
Review: Monitor progress and adjust as needed
SKILL.md
429 lines · 2,116 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 Productivity bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for