plugins/workiq-productivity/skills/email-analytics/SKILL.md
Analyze your email patterns over a time period — volume trends, top senders, response time estimates, busiest days, and unread backlog statistics.
npx skillsauth add microsoft/work-iq email-analyticsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
workiq-ask_work_iq (
question: "What is my profile information including display name and email address?"
)
Extract displayName and mail for report personalization.
Pull all received emails across the analysis period:
workiq-ask_work_iq (
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"Pull all sent emails for response analysis:
workiq-ask_work_iq (
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):
Aggregate the data into the following metrics:
Volume Metrics:
Temporal Patterns:
People Metrics:
Status Metrics:
📊 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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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.
| Parameter | Required | Default | Description |
|-----------|----------|---------|-------------|
| Time period | No | Last 7 days | Analysis window (e.g., "this month", "last 30 days", "this quarter") |
| Include sent | No | true | Whether to analyze outgoing emails too |
| Detail level | No | full | summary (volume only) or full (all sections) |
| Show insights | No | true | Include AI‑generated insights and recommendations |
| MCP Server | Tool | Purpose |
|---|---|---|
| workiq (Local WorkIQ CLI) | ask_work_iq | User identity, email retrieval (received and sent), and message metadata for analytics |
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.
No emails found for the requested period
If ask_work_iq 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_work_iq 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:
ask_work_iq calls).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_work_iq 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.
tools
Preview build of WorkIQ — the full Microsoft 365 tool surface - agentic semantic queries via ask_work_iq PLUS direct, structured reads and writes for emails, meetings, calendar, documents, Teams messages, Planner plans/tasks, OneDrive/SharePoint files, and people. USE THIS SKILL for ANY workplace question or write action where the data lives in Microsoft 365. Read triggers, "what did [person] say", "what are [person]'s priorities", "top of mind from [person]", "what was discussed", "find emails about", "what planner tasks are due", "what meetings do I have", "what documents", "who is working on", "what's the status of", "any updates on". Write triggers, "send email", "reply to [thread]", "forward to", "create a calendar event", "schedule a meeting", "accept/decline the meeting", "mark as read", "delete the draft", "upload to OneDrive", "download attachment". When in doubt about workplace context, try WorkIQ first.
tools
Sub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams development without Slack (use parent skill instead).
tools
Build, test, and deploy code-based Teams apps using the M365 Agents Toolkit CLI. USE FOR: Custom Engine Agents (CEA), Teams bots, tabs, message extensions, Agents Playground local testing, Azure provision/deploy, Slack-to-Teams migration, cross-platform bot development, Block Kit to Adaptive Cards conversion, AI model integration (OpenAI/Azure/Anthropic/Bedrock). DO NOT USE FOR: declarative agents — use the `declarative-agent-developer` skill instead. Triggers: "build a teams bot", "custom engine agent", "CEA", "teams agent", "tab app", "message extension", "test with agents playground", "provision to azure", "deploy to azure", "migrate slack bot", "slack to teams", "convert block kit", "add azure openai to my bot"
development
Query Microsoft 365 Copilot for workplace intelligence - emails, meetings, documents, Teams messages, and people information. USE THIS SKILL for ANY workplace-related question where the answer likely exists in Microsoft 365 data. This includes questions about what someone said, shared, or communicated; meetings, emails, messages, or documents; priorities, decisions, or context from colleagues; organizational knowledge; project status; team activities; or any information that would be in Outlook, Teams, SharePoint, OneDrive, or Calendar. When in doubt about workplace context, try WorkIQ first. Trigger phrases include "what did [person] say", "what are [person]'s priorities", "top of mind from [person]", "what was discussed", "find emails about", "what meetings", "what documents", "who is working on", "what's the status of", "any updates on", etc.