email-analytics

作者: microsoft

分析您在一段时间内的邮件模式——包括数量趋势、主要发件人、回复时间估算、最繁忙的日子以及未读积压统计。

npx skills add https://github.com/microsoft/work-iq --skill email-analytics

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.

来自 microsoft 的更多技能

oss-growth
microsoft
OSS增长黑客角色
agent-framework-azure-ai-py
microsoft
使用Microsoft Agent Framework Python SDK(agent-framework-azure-ai)构建Azure AI Foundry代理。在创建使用AzureAIAgentsProvider的持久化代理、使用托管工具(代码解释器、文件搜索、网络搜索)、集成MCP服务器、管理对话线程或实现流式响应时使用。涵盖函数工具、结构化输出和多工具代理。
development
airunway-aks-setup
microsoft
在AKS上设置AI Runway——从裸集群到运行模型。涵盖集群验证、控制器安装、GPU评估、提供商设置和首次部署。适用场景:“设置AI Runway”、“接入AKS集群”、“安装AI Runway”、“airunway设置”、“将模型部署到AKS”、“在AKS上进行GPU推理”、“在AKS上配置KAITO”、“在AKS上运行LLM”、“在AKS上使用vLLM”、“在AKS上设置模型服务”、“AI Runway控制器”。
devops
appinsights-instrumentation
microsoft
使用Azure Application Insights对Web应用进行插桩的指南。提供遥测模式、SDK设置和配置参考。适用场景:如何对应用进行插桩、App Insights SDK、遥测模式、什么是App Insights、Application Insights指南、插桩示例、APM最佳实践。
devops
applicationinsights-web-ts
microsoft
使用Application Insights JavaScript SDK(@microsoft/applicationinsights-web)为浏览器/Web应用添加检测。用于真实用户监控(RUM)——页面视图、点击、AJAX/fetch依赖项、异常、自定义事件,以及与后端OpenTelemetry追踪关联的浏览器端GenAI代理追踪。涵盖SDK加载器脚本和npm设置、框架扩展(React、React Native、Angular)、点击分析、遥测初始化器,以及从浏览器发出的代理/工具/模型跨度所遵循的OTel GenAI语义约定。
devops
azure-ai-anomalydetector-java
microsoft
使用适用于 Java 的 Azure AI 异常检测器 SDK 构建异常检测应用程序。在实现单变量/多变量异常检测、时间序列分析或 AI 驱动的监控时使用。
development
azure-ai-language-conversations-py
microsoft
使用azure-ai-language-conversations Python SDK实现对话语言理解(CLU)。当使用ConversationAnalysisClient分析对话意图和实体、构建NLP功能或将语言理解集成到应用程序中时使用。
development
azure-ai-ml-py
microsoft
Azure Machine Learning SDK v2 for Python。用于机器学习工作区、作业、模型、数据集、计算资源和管道。 触发词:“azure-ai-ml”、“MLClient”、“工作区”、“模型注册表”、“训练作业”、“数据集”。
development