Email and Inbox skill 05 of 13

Inbox Rules and Filters SKILL.md

The Inbox Rules and Filters skill makes Claude, Codex or another AI agent design filters and rules that sort mail automatically in Gmail, Outlook and other providers. It finds your top senders, sets up five to eight labels or folders based on what you will do, writes and tests rules, highlights priority people, adds exceptions for important alerts, cleans up old mail and reviews rules monthly. It never deletes mail automatically.

inbox-rules-filters/SKILL.md, version 1.0.0, 1,501 words.

Most inboxes mix four very different kinds of mail: messages from people who need the user, automated notifications from tools, newsletters and promotions, and receipts or records. When all four land in one list, important messages get buried and the user must sort by hand every day. Filters and rules sort mail automatically as it arrives, so the main inbox shows mostly what needs a person.

This skill designs filters, labels or folders and rules for Gmail, Outlook and other providers: a small set of destinations, rules based on senders, lists and keywords, priority highlighting for key people, safe testing and a monthly review. It never deletes mail automatically.

Operating principles

  1. Sort by what the user will do, not by topic. Read later, receipts and notifications are actions; dozens of topic folders are not.
  2. Few destinations. Five to eight labels or folders cover most needs.
  3. Never auto-delete. Filters archive or label; deletion stays manual.
  4. Specific rules first. Exact senders and list addresses beat broad keyword rules.
  5. Test, then trust. Check each rule against recent mail before turning it on.

Suggested destinations

Label or folderHoldsSeen when
InboxPeople who need the userEach triage session
VIP (star or highlight)Manager, key clients, familyImmediately or each session
NotificationsTool alerts, system mailDaily or weekly scan
Read laterNewsletters worth keepingWeekly reading slot
ReceiptsOrders, invoices, paymentsMonthly bookkeeping
CalendarInvites and updatesHandled by calendar
ArchiveEverything else after triageSearch only

When to use, and when not to

Use it when the inbox is cluttered by automated mail, important emails get missed, setting up a new account, after an email audit or before giving an AI agent inbox access.

Don't use it for team shared inbox routing (shared-inbox) or for blocking malicious mail (email-security and the provider's spam controls).

Inputs

  • Email provider (Gmail, Outlook, Apple Mail, other).
  • A sample of recent mail, or the top senders by volume.
  • Priority people and topics.
  • Existing labels, folders and rules.
  • Bookkeeping or record-keeping needs.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as inbox-rules-filters/SKILL.md.

---
name: inbox-rules-filters
description: "Design email filters and rules for Gmail, Outlook and other providers: top senders by volume, five to eight action-based labels or folders, sender, list and keyword rules, VIP highlighting, exception rules for important alerts, testing on recent mail, bulk clean-up and a monthly review, never auto-deleting. Use whenever someone wants Gmail filters or Outlook rules, a cleaner inbox, fewer notifications in the main inbox, labels or folders that work, or to set up email before giving an AI agent access."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/email-inbox/inbox-rules-filters/
  category: productivity
  subcategory: email-inbox
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-13"
---

# Inbox Rules and Filters

Most inboxes mix four very different kinds of mail: messages from people who need the user, automated notifications from tools, newsletters and promotions, and receipts or records. When all four land in one list, important messages get buried and the user must sort by hand every day. Filters and rules sort mail automatically as it arrives, so the main inbox shows mostly what needs a person.

This skill designs filters, labels or folders and rules for Gmail, Outlook and other providers: a small set of destinations, rules based on senders, lists and keywords, priority highlighting for key people, safe testing and a monthly review. It never deletes mail automatically.

## Operating principles
1. **Sort by what the user will do, not by topic.** Read later, receipts and notifications are actions; dozens of topic folders are not.
2. **Few destinations.** Five to eight labels or folders cover most needs.
3. **Never auto-delete.** Filters archive or label; deletion stays manual.
4. **Specific rules first.** Exact senders and list addresses beat broad keyword rules.
5. **Test, then trust.** Check each rule against recent mail before turning it on.

## Suggested destinations
| Label or folder | Holds | Seen when |
|---|---|---|
| Inbox | People who need the user | Each triage session |
| VIP (star or highlight) | Manager, key clients, family | Immediately or each session |
| Notifications | Tool alerts, system mail | Daily or weekly scan |
| Read later | Newsletters worth keeping | Weekly reading slot |
| Receipts | Orders, invoices, payments | Monthly bookkeeping |
| Calendar | Invites and updates | Handled by calendar |
| Archive | Everything else after triage | Search only |

## When to use, and when not to
Use it when the inbox is cluttered by automated mail, important emails get missed, setting up a new account, after an email audit or before giving an AI agent inbox access.

Don't use it for team shared inbox routing (`shared-inbox`) or for blocking malicious mail (`email-security` and the provider's spam controls).

## Inputs
- Email provider (Gmail, Outlook, Apple Mail, other).
- A sample of recent mail, or the top senders by volume.
- Priority people and topics.
- Existing labels, folders and rules.
- Bookkeeping or record-keeping needs.

## Workflow

### Step 1. Find the top senders
List senders and mailing lists by volume over the last 30 days, grouped into people, tools, newsletters, receipts and other.

### Step 2. Choose destinations
Start from the suggested set; add only what the user will check.

### Step 3. Write rules
For each high-volume sender or list: condition (from address, list header, subject words) and action (label, skip inbox, mark read, forward).

### Step 4. Highlight priority people
VIP lists, stars or importance markers for named senders so they stand out in every session.

### Step 5. Test
Run each rule's search on the last 30 days; check for false matches before applying.

### Step 6. Apply and clean
Apply to existing mail where useful; archive old notifications in bulk.

### Step 7. Review monthly
Check what still lands in the inbox, adjust rules and remove unused labels.

## Rule examples
| Condition | Action |
|---|---|
| From: notifications@tool.com | Label Notifications, skip inbox |
| List header contains: newsletter-name | Label Read later, skip inbox |
| Subject contains "receipt" OR "invoice" AND from: known vendors | Label Receipts, skip inbox |
| From: manager@company.com | Star, mark important |
| Has calendar invite | Label Calendar |
| To: user is in Cc only AND from: internal domain | Label Cc, keep in inbox but mark lower priority |

## Provider notes
- **Gmail:** create filters from a search (from:, to:, list:, subject:, has:attachment), with actions such as skip inbox, apply label, star, mark important, forward. Labels can be nested.
- **Outlook:** rules with conditions and actions (move to folder, categorise, flag); Focused Inbox separates likely-important mail.
- **Other providers:** most support sender and subject rules; check the help pages for list or header conditions.

## Search operators worth knowing
| Need | Gmail example |
|---|---|
| Bulk mail from one list | list:updates.example.com |
| Old notifications | from:alerts@tool.com older_than:30d |
| Large attachments | larger:10M |
| Unread from a person | from:name@company.com is:unread |

## Output format
```
1. Top senders by volume and type
2. Destinations (labels or folders) with purpose
3. Rules table: condition, action, expected volume
4. VIP list
5. Test results and false matches found
6. Clean-up actions for existing mail
7. Monthly review checklist
```

## Notification digests
Many tools let users choose daily or weekly digests instead of an email per event. Changing these settings at the source is often better than filtering: fewer messages arrive at all. List each noisy tool, check its notification settings, keep only alerts that need action and switch the rest to digests or in-app only.

## Rules for AI agents
Before giving an AI agent access, filters make its work safer and cheaper: notifications and newsletters are already labelled, so triage focuses on people. Keep a label such as "Agent drafted" for drafts the agent creates, so the user can review them in one place.

## Monthly review checklist
- What still reaches the inbox that could be filtered?
- Did any rule hide something important?
- Which labels were never opened? Remove them.
- Are new tools sending mail without a rule?
- Is the VIP list current?

## Keeping it simple
If the user needs a diagram to understand their own rules, there are too many. Merge similar labels, delete rules that move fewer than a few messages a month, and rely on search for the rest. Search is fast enough that most mail never needs a folder.

## Mobile considerations
On phones, show only the main inbox and VIP notifications. Labels such as Notifications and Read later can stay off the phone entirely, which removes much of the temptation to check email between tasks.

## Backing up rules
Export or note every rule in a simple table (condition, action, reason, date added). If an account is moved, rebuilt or shared, the table makes the setup quick to recreate and easy for an agent to audit.

Keep the table with the task files.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Important mail from a noisy tool | Exception rule for alerts with key words (e.g. "failed", "payment") |
| Shared or delegated mailbox | Agree rules with the other users first |
| Records must be kept | Archive and label; never delete |
| Several accounts | Same structure in each, or forward to one |
| Rule catches a real person | Narrow the condition to the exact address |

## Handoffs to related skills
- Find what to filter: `email-system-audit`
- Reduce bulk mail at the source: `newsletter-cleanup`
- Daily sorting of what remains: `inbox-triage`
- Suspicious mail: `email-security`

## Worked example
A product manager received 140 emails a day. The top-sender list showed 52 tool notifications, 31 newsletters, 9 receipts and 48 from people. Seven rules moved notifications to a Notifications label (with an exception for "incident" and "failed"), newsletters to Read later and receipts to Receipts, all skipping the inbox, while the manager and two key stakeholders were starred. Testing found one rule catching a colleague's emails, which was narrowed. The main inbox dropped to about 50 messages a day, almost all from people.

## Common mistakes
- Dozens of topic folders nobody checks.
- Rules that delete mail.
- Broad keyword rules that catch real people.
- No exception for important alerts from noisy tools.
- Never reviewing rules.

## Self-check before you answer
- Do destinations match actions the user will take?
- Was every rule tested on recent mail?
- Are priority people highlighted?
- Does nothing get deleted automatically?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/email-inbox/inbox-rules-filters/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Find the top senders

List senders and mailing lists by volume over the last 30 days, grouped into people, tools, newsletters, receipts and other.

Step 2. Choose destinations

Start from the suggested set; add only what the user will check.

Step 3. Write rules

For each high-volume sender or list: condition (from address, list header, subject words) and action (label, skip inbox, mark read, forward).

Step 4. Highlight priority people

VIP lists, stars or importance markers for named senders so they stand out in every session.

Step 5. Test

Run each rule's search on the last 30 days; check for false matches before applying.

Step 6. Apply and clean

Apply to existing mail where useful; archive old notifications in bulk.

Step 7. Review monthly

Check what still lands in the inbox, adjust rules and remove unused labels.

Rule examples

ConditionAction
From: notifications@tool.comLabel Notifications, skip inbox
List header contains: newsletter-nameLabel Read later, skip inbox
Subject contains "receipt" OR "invoice" AND from: known vendorsLabel Receipts, skip inbox
From: manager@company.comStar, mark important
Has calendar inviteLabel Calendar
To: user is in Cc only AND from: internal domainLabel Cc, keep in inbox but mark lower priority

Provider notes

  • Gmail: create filters from a search (from:, to:, list:, subject:, has:attachment), with actions such as skip inbox, apply label, star, mark important, forward. Labels can be nested.
  • Outlook: rules with conditions and actions (move to folder, categorise, flag); Focused Inbox separates likely-important mail.
  • Other providers: most support sender and subject rules; check the help pages for list or header conditions.

Search operators worth knowing

NeedGmail example
Bulk mail from one listlist:updates.example.com
Old notificationsfrom:alerts@tool.com older_than:30d
Large attachmentslarger:10M
Unread from a personfrom:name@company.com is:unread

Output format

1. Top senders by volume and type
2. Destinations (labels or folders) with purpose
3. Rules table: condition, action, expected volume
4. VIP list
5. Test results and false matches found
6. Clean-up actions for existing mail
7. Monthly review checklist

Notification digests

Many tools let users choose daily or weekly digests instead of an email per event. Changing these settings at the source is often better than filtering: fewer messages arrive at all. List each noisy tool, check its notification settings, keep only alerts that need action and switch the rest to digests or in-app only.

Rules for AI agents

Before giving an AI agent access, filters make its work safer and cheaper: notifications and newsletters are already labelled, so triage focuses on people. Keep a label such as "Agent drafted" for drafts the agent creates, so the user can review them in one place.

Monthly review checklist

  • What still reaches the inbox that could be filtered?
  • Did any rule hide something important?
  • Which labels were never opened? Remove them.
  • Are new tools sending mail without a rule?
  • Is the VIP list current?

Keeping it simple

If the user needs a diagram to understand their own rules, there are too many. Merge similar labels, delete rules that move fewer than a few messages a month, and rely on search for the rest. Search is fast enough that most mail never needs a folder.

Mobile considerations

On phones, show only the main inbox and VIP notifications. Labels such as Notifications and Read later can stay off the phone entirely, which removes much of the temptation to check email between tasks.

Backing up rules

Export or note every rule in a simple table (condition, action, reason, date added). If an account is moved, rebuilt or shared, the table makes the setup quick to recreate and easy for an agent to audit.

Keep the table with the task files.

Edge cases and judgement calls

SituationWhat to do
Important mail from a noisy toolException rule for alerts with key words (e.g. "failed", "payment")
Shared or delegated mailboxAgree rules with the other users first
Records must be keptArchive and label; never delete
Several accountsSame structure in each, or forward to one
Rule catches a real personNarrow the condition to the exact address
  • Find what to filter: email-system-audit
  • Reduce bulk mail at the source: newsletter-cleanup
  • Daily sorting of what remains: inbox-triage
  • Suspicious mail: email-security

Worked example

A product manager received 140 emails a day. The top-sender list showed 52 tool notifications, 31 newsletters, 9 receipts and 48 from people. Seven rules moved notifications to a Notifications label (with an exception for "incident" and "failed"), newsletters to Read later and receipts to Receipts, all skipping the inbox, while the manager and two key stakeholders were starred. Testing found one rule catching a colleague's emails, which was narrowed. The main inbox dropped to about 50 messages a day, almost all from people.

Common mistakes

  • Dozens of topic folders nobody checks.
  • Rules that delete mail.
  • Broad keyword rules that catch real people.
  • No exception for important alerts from noisy tools.
  • Never reviewing rules.

Self-check before you answer

  • Do destinations match actions the user will take?
  • Was every rule tested on recent mail?
  • Are priority people highlighted?
  • Does nothing get deleted automatically?

When to use this skill, and when not to

Use it when automated mail clutters your inbox, important emails get missed, you set up a new account, after an email audit or before giving an AI agent access to your inbox.

Most inboxes mix people, tool notifications, newsletters and receipts in one list. Filters move everything that does not need a person out of the main view as it arrives.

Don’t use it for shared team inbox routing or for blocking malicious mail; see Email Security.

Example prompts

  • “Set up Gmail filters for my notifications and newsletters.”
  • “Write Outlook rules so only people reach my inbox.”
  • “Which senders should I filter?”
  • “Make sure alerts about failed payments still reach me.”
  • “Clean up my labels; I have too many.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

Top senders (30 days): 52 tool notifications, 31 newsletters, 9 receipts, 48 people
Rules: 7 (notifications, newsletters, receipts skip inbox)
Exception: alerts containing incident or failed stay in inbox
VIP: manager and two key stakeholders starred
Test: one rule caught a colleague, narrowed
Result: about 50 emails a day reach the inbox, mostly people

Every rule is tested against recent mail before it is turned on, and nothing is ever deleted automatically.

What the agent needs from you

The skill asks for your email provider, a sample of recent mail or top senders by volume, your priority people and topics, existing labels and rules and any bookkeeping or record-keeping needs.

How this skill hands off to related skills

Inbox Rules and Filters connects to the Email System Audit, Newsletter Clean-Up, Inbox Triage and Email Security.

How to run Inbox Rules and Filters step by step

  1. Install the skill as inbox-rules-filters/SKILL.md.
  2. List top senders for 30 days.
  3. Choose a few destinations.
  4. Write and test rules.
  5. Highlight priority people.
  6. Review monthly.

Situations this skill handles

Inboxes differ. The skill handles these:

SituationWhat the skill does
Important alerts from noisy toolsException rules
Shared mailboxRules agreed first
Records must be keptArchive and label
Several accountsSame structure in each
Rule catches a personNarrowed to exact address
Too many labelsMerged and searched

What makes this skill different

Most filter guides list features. This skill starts from your top senders and what you will actually do with each kind of mail, tests every rule before use and adds exceptions so important alerts never disappear.

It also prepares the inbox for an AI agent, so triage focuses on people.

Practical tips from real projects

  • Sort by action, not topic.
  • Few destinations.
  • Never auto-delete.
  • Test, then trust.

A worked example: a product manager received 140 emails a day. The top-sender list showed 52 tool notifications, 31 newsletters, 9 receipts and 48 messages from people. Seven rules moved notifications, newsletters and receipts to their own labels, skipping the inbox, with an exception for alerts mentioning an incident or a failure. The manager and two key stakeholders were starred. Testing found one rule catching a colleague's emails, which was narrowed to an exact address. The main inbox dropped to about 50 messages a day, almost all from people.

Suggested destinations follow actions: the inbox for people who need the user, a VIP star or highlight for the manager, key clients and family, Notifications for tool alerts checked daily or weekly, Read later for newsletters, Receipts for monthly bookkeeping, Calendar for invites and Archive for everything else, found by search.

Rules use specific conditions first: exact sender addresses and list headers beat broad keywords. Examples include moving mail from a tool's notification address to Notifications, newsletters identified by their list header to Read later, receipts and invoices from known vendors to Receipts, and starring the manager.

In Gmail, filters are created from a search using operators such as from, to, list, subject and has attachment, with actions to skip the inbox, apply a label, star, mark important or forward. Outlook rules move to folders, categorise or flag, and Focused Inbox separates likely-important mail.

Changing notification settings at the source is often better than filtering, because many tools offer daily or weekly digests. Before connecting an AI agent, filters make triage cheaper and safer, and a label for agent drafts keeps review in one place. A monthly check asks what still reaches the inbox, whether any rule hid something important, which labels were never opened and whether new tools need rules, and every rule is recorded in a simple table so the setup can be rebuilt quickly.

On phones, only the main inbox and VIP alerts need to be visible; labels such as Notifications and Read later can stay off mobile entirely, which removes much of the urge to check email between tasks. When rules grow so complex that the user needs a diagram to understand them, similar labels are merged and rules that move only a few messages a month are deleted.

Edge cases are handled with care. Important alerts from noisy tools get exception rules for words such as failed, payment or incident. Shared or delegated mailboxes need rules agreed with the other users first. Where records must be kept, mail is archived and labelled, never deleted. People with several accounts use the same structure in each or forward everything to one inbox, and any rule that catches a real person is narrowed to the exact sender address before it is switched back on.

Rules are kept simple enough to understand at a glance, and the rule table is stored with the task files so an agent can audit it.

Once filters are in place, most people find that their main inbox shows mainly real conversations, which makes every triage session faster and calmer.

Frequently asked questions

Tool notifications, newsletters and receipts, each moved to its own label and out of the main inbox.

Usually five to eight, based on what you will do with the mail, with search for everything else.

No. Filters should label or archive; deletion stays manual.

Add exception rules for key words such as failed or incident so those alerts stay in the inbox.

Yes. Outlook rules support conditions and actions such as move, categorise and flag.

Monthly: check what still reaches the inbox, what was hidden wrongly and which labels are unused.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.