Email Analytics logo

Email Analytics

OrganizationPopular
microsoft
email-analytics

Analyze your email patterns over a time period — volume trends, top senders, response time estimates, busiest days, and unread backlog statistics.

Overview

Publishermicrosoft
Repositorywork-iq
Skill nameemail-analytics
Stars
1K
Forks
140
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by microsoft on GitHub. Read the source before you install it.

Installation

Install the Email Analytics AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/microsoft/work-iq/tree/main/plugins/workiq-productivity/skills/email-analytics
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/microsoft/work-iq.git /tmp/work-iq
mkdir -p .claude/skills
cp -r /tmp/work-iq/plugins/workiq-productivity/skills/email-analytics .claude/skills/email-analytics
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email Analytics in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Email Analytics on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Email Analytics is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Email Analytics

Get a data‑driven view of your email life. This skill scans your inbox and sent folder over a time period, crunches the numbers, and presents a formatted analytics dashboard — volume by day, top senders, response patterns, busiest hours, flagged backlogs, and unread trends. Use it to understand your communication load and identify where your email time goes.

When to Use

  • "Analyze my email patterns this month"
  • "How many emails did I get last week?"
  • "Who sends me the most email?"
  • "Show me my email volume trends"
  • "Give me inbox statistics for the last 30 days"
  • "What does my email workload look like?"

Instructions

Step 1: Identify the User

workiq-ask (
  question: "What is my profile information including display name and email address?"
)

Extract displayName and mail for report personalization.

Step 2: Retrieve Received Emails

Pull all received emails across the analysis period:

workiq-ask (
  question: "List all emails I received in the last <time period>. For each email include the sender name and email, subject, received date and time, read/unread status, importance level, whether it has attachments, and flag status."
)

For longer periods, run multiple queries to capture the full window:

  • "List all emails I received this week with sender, subject, date, read status, importance, attachments, and flag status"
  • "List all emails I received last week with sender, subject, date, read status, importance, attachments, and flag status"
  • etc.

Step 3: Retrieve Sent Emails

Pull all sent emails for response analysis:

workiq-ask (
  question: "List all emails I sent in the last <time period>. For each email include the recipients, subject, sent date and time, and whether it has attachments."
)

Collect for each message (received and sent):

  • From / To — sender and recipient addresses
  • ReceivedDateTime — timestamp for volume trends
  • IsRead — read vs. unread status
  • Importance — high/normal/low
  • HasAttachments — attachment tracking
  • Flag status — flagged items count
  • Subject — for thread grouping

Step 4: Compute Analytics

Aggregate the data into the following metrics:

Volume Metrics:

  • Total received, total sent
  • Daily average received / sent
  • Ratio of received to sent

Temporal Patterns:

  • Volume by day of week (Mon–Sun)
  • Peak hours (morning, afternoon, evening)
  • Busiest single day

People Metrics:

  • Top 10 senders by volume
  • Top 10 recipients you email most
  • Emails from direct manager

Status Metrics:

  • Unread count and percentage
  • Flagged count
  • High importance count
  • Emails with attachments

Step 5: Present the Analytics Dashboard

📊 EMAIL ANALYTICS — {displayName}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 Period: {start date} → {end date} ({N} days)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📬 VOLUME OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  📥 Received:     {total received}    ({daily avg}/day)
  📤 Sent:         {total sent}        ({daily avg}/day)
  📈 Ratio:        {received:sent ratio}
  📬 Unread:       {unread count}      ({unread %}%)
  🚩 Flagged:      {flagged count}
  ⚡ High Priority: {high importance count}

📅 VOLUME BY DAY OF WEEK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Mon │ ████████████████████░░░░░  82
  Tue │ ███████████████████████░░  94  ← busiest
  Wed │ ██████████████████░░░░░░░  73
  Thu │ █████████████████████░░░░  86
  Fri │ ██████████████░░░░░░░░░░░  58
  Sat │ ███░░░░░░░░░░░░░░░░░░░░░  12
  Sun │ ██░░░░░░░░░░░░░░░░░░░░░░   8

👤 TOP SENDERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  #1  Firstname1 Lastname1    │ 34 emails │ ████████████████
  #2  notifications@jira     │ 28 emails │ █████████████
  #3  Firstname2 Lastname2   │ 22 emails │ ██████████
  #4  Firstname3 Lastname3   │ 18 emails │ ████████
  #5  build-alerts@ci        │ 15 emails │ ███████
  #6  Firstname4 Lastname4   │ 14 emails │ ██████
  #7  calendar@outlook       │ 12 emails │ █████
  #8  Firstname5 Lastname5   │ 10 emails │ ████
  #9  newsletter@company     │  9 emails │ ████
  #10 help-desk@contoso      │  7 emails │ ███

👤 TOP RECIPIENTS (your sent mail)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  #1  Firstname1 Lastname1    │ 19 emails
  #2  Firstname2 Lastname2   │ 14 emails
  #3  Manager: Firstname6 Lastname6 │ 11 emails
  #4  Firstname3 Lastname3   │  9 emails
  #5  Team DL                │  8 emails

📎 ATTACHMENT STATS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  📎 Emails with attachments: {count} ({percentage}%)
  📊 Most common types:       PDF, XLSX, DOCX

🔍 INSIGHTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  💡 Tuesday is your busiest email day — consider blocking focus time.
  💡 {unread count} unread emails — consider triaging your inbox.
  💡 {percentage}% of received email is from automated systems.
  💡 You send {ratio} emails for every {N} received.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Output Format

A formatted analytics dashboard with bar charts for volume trends, ranked sender/recipient tables, attachment statistics, and actionable insights. Bar charts use Unicode block characters for visual representation.

Parameters

ParameterRequiredDefaultDescription
Time periodNoLast 7 daysAnalysis window (e.g., "this month", "last 30 days", "this quarter")
Include sentNotrueWhether to analyze outgoing emails too
Detail levelNofullsummary (volume only) or full (all sections)
Show insightsNotrueInclude AI‑generated insights and recommendations

Required MCP Tools

MCP ServerToolPurpose
workiq (Local WorkIQ CLI)askUser identity, email retrieval (received and sent), and message metadata for analytics

Tips

  • Run weekly for a quick health check on your email workload, or monthly for trend spotting.
  • High automated‑email percentage? Consider unsubscribing or filtering newsletter noise.
  • Compare week‑over‑week by running twice with different date ranges.
  • The insights section auto‑detects patterns like automated senders, unread backlogs, and busiest days to give you actionable advice.
  • If email peaks align with meeting‑heavy days, you may need more focus time.

Examples

Last 7 days at a glance

"Analyze my email patterns for the last week"

Returns a full dashboard covering the past 7 days — total received and sent, top senders, busiest day, unread count, and key insights like automated-email percentage.


Monthly deep-dive

"Give me inbox statistics for March"

Runs a 31-day analysis, identifying volume trends by day of week, ranking your top 10 senders, and flagging any growing unread backlog. Useful for end-of-month reporting or planning the next sprint.


Quick sender check

"Who sends me the most email this quarter?"

Focuses the output on the Top Senders table. Even when requesting a narrow slice, the full dashboard is generated — scroll to the TOP SENDERS section or ask for detail level: summary to limit output to volume and sender rankings only.

Error Handling

No emails found for the requested period If ask returns no email results, verify the time period phrasing (e.g., use "last 30 days" instead of a specific date range). The query is natural-language driven — overly precise date strings may not match. Retry with a broader phrase.

Incomplete or partial data If ask returns fewer results than expected or omits certain metadata fields, compute analytics on the available data. Append a note to the dashboard: "Some messages could not be fully retrieved and were excluded from analysis."

Large volumes causing slow response For periods longer than 90 days or inboxes with very high traffic (1 000+ messages), a single query may return incomplete results. In this case:

  • Reduce the analysis window (e.g., analyze one month at a time with separate ask calls).
  • Use detail level: summary to rely on aggregate counts only.

Sent folder unavailable If the sent-mail query returns no results and the user expects sent data, confirm that the account's Sent Items folder is accessible. Set include sent: false to proceed with received-email analytics only.

Identity lookup failure If ask cannot resolve the user profile, the dashboard still generates but displays the email address (from email results) instead of the display name. No analytics data is lost.

Frequently asked questions

What does the Email Analytics AI skill do?

Analyze your email patterns over a time period — volume trends, top senders, response time estimates, busiest days, and unread backlog statistics.

Why use Email Analytics on TypingMind?

Because you install it once and use it with any model. Email Analytics is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Email Analytics in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/microsoft/work-iq/tree/main/plugins/workiq-productivity/skills/email-analytics. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Email Analytics?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Email Analytics?

As many as you like. As long as a model supports skills, you can use Email Analytics with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Email Analytics AI skill free?

It is published on GitHub by microsoft. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇