Agent skill

Email Check

by AgriciDaniel in AgriciDaniel/claude-email

Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance…

MITAuto-check passedProductivity & Automation

Install Email Check

skills CLI
$ npx skills add AgriciDaniel/claude-email --skill email-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgriciDaniel/claude-email email-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-email.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-check .claude/skills/email-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-check
GitHub stars
130
Token cost
~2.4k tokens
SKILL.md length
908 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance…

  • Works in 7 steps: Detect Available Email Provider → Fetch Unread Emails → Batch Fetch Email Content → …
  • The user wants to check email
  • SKILL.md covers Purpose, Workflow, Scoring Signal Reference and Reply Suggestion Guidelines, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Email Check is an agent skill from AgriciDaniel/claude-email. Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance, categorizes into Urgent/Important/Routine/Archive, and generates reply suggestions for top priority items. Use when the user wants to check email, review inbox, triage messages, see what's urgent, or get reply suggestions. Triggers on check email, inbox triage, what's important, email summary, unread emails, priority…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Email management. It works with Gmail and Model Context Protocol. The repository describes itself as: AI-powered email management and marketing skill for Claude Code. Inbox triage, composition, quality review, deliverability audit, automation sequences, and marketing strategy. The licence is MIT.

When your agent uses it

  • The user wants to check email
  • Triage messages
  • See whats urgent
  • Get reply suggestions

Example prompts

  • “/email-check”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Detect Available Email Provider
  2. Fetch Unread Emails
  3. Batch Fetch Email Content
  4. Score Each Email (0-100)
  5. Categorize Emails
  6. Generate Reply Suggestions
  7. Output Format

What it can do on your machine

Read from SKILL.md and the folder at commit 182270a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Check loads about 2.4k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 908 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~133
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-email at commit 182270a, republished under its MIT licence (© AgriciDaniel). 908 words, ~2,416 tokens.

Download SKILL.mdSave it as .claude/skills/email-check/SKILL.md (or your agent's skills folder).
name
email-check
description
Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance, categorizes into Urgent/Important/Routine/Archive, and generates reply suggestions for top priority items. Use when the user wants to check email, review inbox, triage messages, see what's urgent, or get reply suggestions. Triggers on check email, inbox triage, what's important, email summary, unread emails, priority inbox.
allowed-tools
Read, Grep, Glob
user-invocable
false

Email Check Sub-Skill

Purpose

This sub-skill handles intelligent inbox triage by connecting to Gmail or Outlook via MCP, analyzing unread emails, scoring them by importance, categorizing them, and generating reply suggestions for high-priority items.

Workflow

1. Detect Available Email Provider

Check which MCP tools are available:

  • Gmail: search_gmail_messages, get_gmail_messages_content_batch, get_gmail_thread_content, list_gmail_labels
  • Outlook: list-mail-messages, list-mail-folder-messages, get-mail-message

Prefer Gmail if both are available (better batch operations).

2. Fetch Unread Emails

For Gmail:

search_gmail_messages(query="is:unread", max_results=50)

For Outlook:

list-mail-messages (defaults to recent messages, filter for unread)
3. Batch Fetch Email Content

For Gmail:

get_gmail_messages_content_batch(message_ids=[...])  # Up to 25 at a time

If more than 25 unread, prioritize most recent first.

For Outlook:

get-mail-message for each message (sequential)

Limit to 25 emails maximum to avoid overwhelming analysis.

4. Score Each Email (0-100)

Apply the following scoring algorithm:

Base Score: 50
Sender Recognition (+20 to -20)
  • +20: VIP/known contact (domain matches user's company, appears in sent folder frequently)
  • +10: Recognized sender (has prior thread history)
  • 0: Unknown sender with legitimate domain
  • -15: Newsletter/automated sender (bulk email headers, unsubscribe links)
  • -20: Notification sender (no-reply@, noreply@, automated@)
Direct Address (+15 to -10)
  • +15: Primary recipient (To: field)
  • 0: CC'd (CC: field)
  • -10: BCC'd or mass email (many recipients)
Thread Depth (+10)
  • +10: Reply in active thread (Re: subject, multiple messages in thread)
  • 0: New email (no thread history)
Urgency Keywords (+15)

Check subject and first 200 characters for:

  • urgent, ASAP, deadline, action required, immediate, time-sensitive, expiring, expires, due
  • +15 if any urgency keyword found
Calendar/Meeting (+20)
  • +20: Calendar invite, meeting request, event notification
  • Detect via attachments (ics file) or subject patterns (Invitation:, Meeting:)
Deadline Detection (+25)

Parse email body for dates/deadlines:

  • +25: Deadline within 48 hours
  • +10: Deadline within 7 days
  • 0: No deadline or deadline > 7 days
Business Relevance (+15 to -10)

If email-profile.md exists in parent directory:

  • +15: Mentions user's key topics, clients, projects
  • +5: Industry-relevant keywords
  • -10: Off-topic or personal (if business inbox)
Final Score Calculation

Sum all adjustments to base score of 50. Clamp to 0-100 range.

5. Categorize Emails

Based on final score:

Score RangeCategoryAction
85-100UrgentImmediate attention, generate reply suggestions
65-84ImportantReview soon, may need action
40-64RoutineNormal priority, review when available
20-39Low PrioritySkim or defer
0-19ArchiveLikely noise or automated
6. Generate Reply Suggestions

For emails scored 85+ (Urgent category):

  1. Read full thread context using get_gmail_thread_content or equivalent
  2. Check for email-profile.md in parent directory for user's:
    • Brand voice (professional, casual, direct, warm)
    • Common sign-off
    • Industry/role context
  3. Draft two reply options:
    • Brief: 1-2 sentences, direct answer
    • Detailed: 1 paragraph with context

Do NOT draft replies if:

  • Email requires research beyond available context
  • Email needs user decision (approve/decline, choose option)
  • Email is FYI/informational only
  • Email is calendar invite (suggest accept/decline/tentative instead)

In these cases, output: "This email requires your personal attention: [reason]"

7. Output Format
markdown
## Inbox Summary

**X unread emails** | Y Urgent | Z Important | W Routine | V Low Priority

### Urgent (Action Required)

| # | From | Subject | Score | Suggested Action |
|---|------|---------|-------|------------------|
| 1 | sender@domain.com | Subject line | 95 | [Reply/Review/Respond] |
| 2 | ... | ... | 88 | ... |

---

### Important

| # | From | Subject | Score | Category |
|---|------|---------|-------|----------|
| 3 | ... | ... | 78 | Meeting follow-up |
| 4 | ... | ... | 70 | Client inquiry |

---

### Routine & Low Priority

- **Routine (40-64)**: X emails - [grouped summary by sender/topic]
- **Low Priority (20-39)**: Y emails - newsletters, notifications
- **Archive (<20)**: Z emails - automated/noise

---

### Suggested Replies

#### 1. Re: [Subject] (to: sender@domain.com)

**Context:** [Why this email scored high, key points]

**Brief Option:**
> [1-2 sentence reply]
>
> [Sign-off]

**Detailed Option:**
> [Paragraph with more context/explanation]
>
> [Sign-off]

#### 2. Re: [Next urgent email]

[Repeat format]

---

### Emails Requiring Personal Attention

- **#X - [Subject]**: Needs decision on [topic]
- **#Y - [Subject]**: Requires research before responding

Scoring Signal Reference

SignalScore ImpactDetection
Direct To: address+15Check To: field
VIP/known sender+20Domain match, sent folder history
Active thread+10Thread ID, Re: in subject
Urgency keywords+15Subject/body scan
Calendar invite+20.ics attachment, invite headers
Deadline <48h+25Date parsing in body
Deadline <7d+10Date parsing in body
Business relevance+15Match email-profile.md topics
CC'd (not primary)-10CC: field
Newsletter-20Unsubscribe link, bulk headers
Notification-15no-reply@ sender
Unknown sender-10No thread history

Reply Suggestion Guidelines

Show full SKILL.md (371 more words)Show less
Tone Adaptation

If email-profile.md exists, adapt replies to match:

  • Professional: Formal, structured, clear
  • Casual: Friendly, conversational
  • Direct: Brief, action-oriented
  • Warm: Personable, relationship-focused

Default to professional-friendly if no profile exists.

Reply Structure

Brief Option:

  • Answer the core question/request
  • 1-2 sentences maximum
  • Clear next step if needed

Detailed Option:

  • Address all points raised
  • Provide context or explanation
  • 1 paragraph (3-5 sentences)
  • Suggest next steps or timeline
When NOT to Draft
  • Email asks for approval/decision → Suggest: "Review and approve/decline X"
  • Email requires data you don't have → "This email requires your personal attention: needs [data/info]"
  • Email is complex multi-part → "This email requires your personal attention: multiple decisions needed"
  • Email is FYI only → Suggested Action: "Review (no response needed)"

Error Handling

No MCP Connection

If neither Gmail nor Outlook MCP is available:

Error: No email provider connected. Please ensure Gmail MCP or Outlook MCP is configured.
Empty Inbox
## Inbox Summary
**0 unread emails** - Your inbox is clear!
MCP Rate Limits

If batch fetch fails, fall back to individual message retrieval (slower but reliable).

Thread Context Unavailable

If get_gmail_thread_content fails, draft replies based on single message only (note: "Limited context - single message view").

Integration Points

email-profile.md (optional)

If exists in parent directory (../email-profile.md), use for:

  • Brand voice detection
  • Business relevance scoring
  • Reply tone/style matching
  • Common topics/clients list
Gmail-Specific Features
  • Use labels to refine categorization (e.g., skip "Promotions" labeled emails)
  • Check sent folder for sender recognition
Outlook-Specific Features
  • Use folder structure for context (Inbox vs Focused)
  • Leverage categories if available

Performance Optimization

  • Batch fetch 25 emails at a time (Gmail)
  • Limit analysis to 50 most recent unread
  • Cache sender recognition data during session
  • Prioritize most recent emails if >50 unread

Output Constraints

  • Keep total output under 2000 lines
  • Group routine/low priority emails by topic/sender
  • Only show full details for Urgent and Important categories
  • Collapse archived emails into summary count

Quality Gates

Before outputting digest:

  1. Verify all urgency scores are justified with signal breakdown
  2. Ensure reply suggestions are actionable (not generic)
  3. Check that "personal attention" notes explain why
  4. Confirm categories align with score ranges
  5. Validate that batch operations completed successfully

Success Criteria

A successful email check session should:

  • Identify all truly urgent emails (no false negatives)
  • Minimize false positives in Urgent category (precision > 80%)
  • Provide actionable reply drafts for top 3-5 emails
  • Complete analysis in <30 seconds for 25 emails
  • Output clear next actions for each category

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/email-check of AgriciDaniel/claude-email.

Open the folder on GitHubat commit 182270a

Compare with similar skills

Email Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Check this skillAgriciDaniel/claude-email130—~2.4kAutomated safety check: PassMIT
Gmail Query Syntaxprovos/ironcurtain612—~971Automated safety check: PassApache-2.0
Setup Lanes Linklanes-sh/app273—~2.3kAutomated safety check: PassNone
Triage Inboxpedrohcgs/claude-code-my-workflow1.7k—~2.7kAutomated safety check: NotesMIT
Ops Inboxdavepoon/buildwithclaude3.6k—~7.2kAutomated safety check: NotesMIT
Connectorsautonomous-ai/Physical-AI-Operating-System381—~10kAutomated safety check: NotesApache-2.0

Similar skills

  • Gmail Query Syntax

    provos/ironcurtain

    Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose.

    612 GitHub stars~971 tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Setup Lanes Link

    lanes-sh/app

    A skill your agent uses when installing or standing up Lanes Link, the self-hostable MCP endpoint that gives an agent someone's own accounts, memory, tasks, assets, skills, identity and vault.

    273 GitHub stars~2.3k tokensUpdated 3 days ago
    Productivity & AutomationAuto-check passed
  • Triage Inbox

    pedrohcgs/claude-code-my-workflow

    Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor…

    1.7k GitHub stars~2.7k tokensUpdated 11 days ago
    Productivity & AutomationAuto-check: notes
  • Ops Inbox

    davepoon/buildwithclaude

    Full inbox management across all channels — WhatsApp (wacli), Email (Gmail MCP), Slack (MCP), Telegram (user-auth MCP), Discord (webhook + REST read), Notion (MCP — comments, mentions, assigned…

    3.6k GitHub stars~7.2k tokensUpdated today
    Productivity & AutomationAuto-check: notes
  • Connectors

    autonomous-ai/Physical-AI-Operating-System

    Discover and use linked third-party services (Gmail, Google Calendar, Google Drive, Notion, Figma, Asana, Linear, GitHub, Ahrefs, Facebook Fan Page and others).

    381 GitHub stars~10k tokensUpdated today
    Productivity & AutomationAuto-check: notes
  • Add Gmail

    sbusso/claudeclaw

    Add Gmail integration to ClaudeClaw. An agent skill from sbusso/claudeclaw.

    194 GitHub stars~1.9k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from AgriciDaniel/claude-email

  • Email Plan

    AgriciDaniel/claude-email

    Generate comprehensive email marketing strategy with 90-day implementation roadmap.

    130 GitHub stars~4.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Email Audit

    AgriciDaniel/claude-email

    Audits email domain deliverability setup (SPF, DKIM, DMARC, MX records, blacklists, TLS) and generates health score (0-100) with prioritized fix list.

    130 GitHub stars~3k tokensUpdated 4 mo ago
    Auto-check: notes
  • Email Review

    AgriciDaniel/claude-email

    Pre-send email quality review and scoring across 5 dimensions (subject line, copy quality, technical/HTML, deliverability, compliance).

    130 GitHub stars~3.3k tokensUpdated 4 mo ago
    Auto-check: notes
  • Email Sequence

    AgriciDaniel/claude-email

    Designs complete email automation sequences with timing, subject lines, copy, and conditional logic.

    130 GitHub stars~2.8k tokensUpdated 4 mo ago
    Auto-check passed
  • Email

    AgriciDaniel/claude-email

    Comprehensive email management and marketing for any business type.

    130 GitHub stars~2k tokensUpdated 4 mo ago
    Auto-check: notes
  • Email Write

    AgriciDaniel/claude-email

    Compose high-converting emails using proven copy frameworks (PAS, AIDA, BAB, FAB, 4Ps).

    130 GitHub stars~2.8k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Email Check

What does Email Check do?

Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance…. Email Check is an agent skill from AgriciDaniel/claude-email. Intelligent inbox triage that connects to Gmail or Outlook, scores emails by importance (0-100) using sender recognition, urgency keywords, thread depth, time sensitivity, and business relevance, categorizes into Urgent/Important/Routine/Archive, and generates reply suggestions for top priority items.

When should I use Email Check?

Email Check fits situations like: the user wants to check email; triage messages; see whats urgent; get reply suggestions.

How do I install Email Check in Claude Code?

Run `npx skills add AgriciDaniel/claude-email --skill email-check -a claude-code`. Or copy the skill folder (skills/email-check in AgriciDaniel/claude-email) into .claude/skills/email-check in your project. Claude Code loads it when a task matches its description.

How do I install Email Check in Codex?

Run `npx skills add AgriciDaniel/claude-email --skill email-check -a codex`. Or copy the skill folder (skills/email-check in AgriciDaniel/claude-email) into .agents/skills/email-check in your project. Codex loads it when a task matches its description.

Can I use Email Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-email --skill email-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-check, .gemini/skills/email-check, .github/skills/email-check and .opencode/skills/email-check in your project.

What does Email Check need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Check is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob.

Does Email Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Email Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Email Check use?

Email Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Check use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Check?

Skills that share tags, products or a category with Email Check: Gmail Query Syntax (provos/ironcurtain, 612 stars), Setup Lanes Link (lanes-sh/app, 273 stars), Triage Inbox (pedrohcgs/claude-code-my-workflow, 1.7k stars) and Ops Inbox (davepoon/buildwithclaude, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Check?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-email, which has 130 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on May 23, 2026.

Source: AgriciDaniel/claude-email on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.