stats
This skill should be used when the user asks for "email stats", "inbox stats", "email analytics", "how many unread", or wants to see inbox metrics. Shows unread count, top senders, oldest unread, and volume trends.
npx skills add majiayu000/claude-skill-registry --skill stats-data-wise-himalaya-mcp --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /email:stats - Inbox Statistics Get a quick overview of your inbox: unread count, volume, top senders, and oldest unread. ## Usage ``` /email:stats # Current inbox snapshot /email:stats --weekly # Include week-over-week comparison /email:stats --folder Sent # Stats for a specific folder ``` ## When Invoked 1. Call `list_emails` with `page_size: 50` to get recent emails 2. Call `search_emails` with `not flag Seen` to get unread count 3. Compute statistics from the results: - Total unread count - Today's email count - Yesterday's email count - Top senders (by frequency in recent emails) - Oldest unread email (date and sender) 4. If `--weekly` flag: call `list_emails` for previous week and compare 5. Display formatted statistics ## MCP Tools Used - `list_emails` — to get recent envelopes and counts - `search_emails` — to filter by unread status and date ranges ## Output Format ``` 📊 Inbox Stats Unread: 47 (12 today, 8 yesterday) Total recent: 156 emails (last 7 days) Top senders: 1. boss@company.com — 6 emails 2. team@company.com — 4 emails 3. newsletter@dev.to — 3 emails 4. github@notifications — 3 emails 5. ci@builds.io — 2 emails Oldest unread: 12 days ago From: hr@company.com S
- Usage
- When Invoked
- MCP Tools Used
- Output Format
- Weekly Comparison (--weekly)
What does the stats skill do?
This skill should be used when the user asks for "email stats", "inbox stats", "email analytics", "how many unread", or wants to see inbox metrics. Shows unread count, top senders, oldest unread, and volume trends.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill stats-data-wise-himalaya-mcp --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.