npx skills add https://github.com/claude-office-skills/skills --skill 'Email Classifier'自动分类和优先处理邮件,帮助管理收件箱过载问题。
此技能可帮助您:
| 类别 | 描述 | 示例 |
|---|---|---|
| 需要行动 | 需要您回复/采取行动 | 请求、审批、问题 |
| 仅供参考 | 信息性,无需行动 | 更新、公告、报告 |
| 等待中 | 您正在等待他人回复 | 跟进、待回复事项 |
| 已委派 | 转发给其他人处理 | 收件人错误、团队事务 |
| 归档 | 保留但无需行动 | 确认函、收据 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 删除 | 低价值,可移除 | 垃圾邮件、无关推广 |
| 类型 | 描述 |
|---|---|
| 会议 | 邀请、更新、取消 |
| 任务/请求 | 有人要求您做某事 |
| 问题 | 需要您回答 |
| 更新/报告 | 状态更新、进度报告 |
| 审批 | 需要您签字批准 |
| 新闻简报 | 订阅内容 |
| 营销 | 推广内容 |
| 警报/通知 | 系统警报、通知 |
| 个人 | 与工作无关 |
| 垃圾邮件/钓鱼邮件 | 不需要或可疑的邮件 |
| 优先级 | 响应时间 | 指标 |
|---|---|---|
| 🔴 紧急 | 数小时内 | 今日截止、高管要求、阻塞性问题 |
| 🟠 高 | 24小时内 | 重要客户、时间敏感、直接请求 |
| 🟡 普通 | 一周内 | 标准请求、常规事务 |
| 🟢 低 | 方便时处理 | 仅供参考、新闻简报、非紧急更新 |
"Classify this email: [粘贴邮件内容]"
"Classify these emails and organize by priority:
1. [邮件 1]
2. [邮件 2]
3. [邮件 3]"
"Classify my emails. Treat anything from @client.com as high priority"
## Email Classification
**From**: sender@example.com
**Subject**: Q1 Budget Approval Needed
| Attribute | Value |
|-----------|-------|
| **Category** | Action Required |
| **Type** | Approval |
| **Priority** | 🔴 Urgent |
| **Deadline** | EOD Friday |
| **Sender Importance** | High (CFO) |
### Recommended Action
Review attached budget and approve/reject by Friday EOD.
### Suggested Response Time
Within 4 hours
### Labels/Tags
`finance`, `approval`, `q1-budget`, `executive`
## Email Classification Results
**Total Emails**: 15
**Processing Date**: 2026-01-29
### Summary
| Category | Count | % |
|----------|-------|---|
| Action Required | 4 | 27% |
| FYI | 6 | 40% |
| Delete/Spam | 3 | 20% |
| Waiting | 2 | 13% |
### 🔴 Urgent (2)
1. **[Subject]** from [Sender] - [Action needed]
2. **[Subject]** from [Sender] - [Action needed]
### 🟠 High Priority (3)
1. **[Subject]** from [Sender] - [Type]
2. ...
### 🟡 Normal (5)
1. ...
### 🟢 Low/FYI (5)
1. ...
## My Email Rules
### VIP Senders (Always High Priority)
- CEO, CFO, CTO
- Direct manager
- Key clients: @bigclient.com
### Auto-Archive
- Newsletters (unless from [specific])
- Automated reports (after reading)
- CC-only emails (if no @mention)
### Auto-Delegate
- IT support requests → it-team@
- HR questions → hr@
### Red Flags (Mark Urgent)
- "URGENT" in subject
- Legal/compliance mentions
- Customer complaints
## Suspicious Email Indicators
**Risk Level**: 🔴 High / 🟠 Medium / 🟢 Low
### Red Flags Detected
- [ ] Sender domain doesn't match display name
- [ ] Urgency pressure tactics
- [ ] Request for credentials/personal info
- [ ] Suspicious links (hover to check)
- [ ] Unexpected attachments
- [ ] Grammar/spelling errors
- [ ] Generic greeting ("Dear Customer")
### Recommendation
[Do not click links / Report as phishing / Safe to proceed]
## Recommended Processing Order
### Morning (30 min)
1. 🔴 Urgent emails first (2 emails, ~10 min)
2. 🟠 High priority (3 emails, ~15 min)
3. Quick wins under 2 min (5 emails, ~5 min)
### Batch Later
- 🟡 Normal priority - schedule 1 hour block
- 🟢 Newsletters - end of day or weekend
### Delegate Now
- Forward [Email X] to [Person] for handling
📁 Inbox
├── 📁 Action Required
│ ├── 📁 Today
│ ├── 📁 This Week
│ └── 📁 Waiting For Response
├── 📁 FYI / Read
├── 📁 Reference
│ ├── 📁 Projects
│ ├── 📁 Clients
│ └── 📁 Receipts
└── 📁 Newsletters
每周安装
0
仓库
GitHub 星标
5
首次出现
1970年1月1日
安全审计
Automatically categorize and prioritize emails to help manage inbox overload.
This skill helps you:
| Category | Description | Examples |
|---|---|---|
| Action Required | Needs your response/action | Requests, approvals, questions |
| FYI | Informational, no action needed | Updates, announcements, reports |
| Waiting | You're waiting for others | Follow-ups, pending responses |
| Delegated | Forward to someone else | Wrong recipient, team matters |
| Archive | Keep but no action | Confirmations, receipts |
| Delete | Low value, can remove | Spam, irrelevant promos |
| Type | Description |
|---|---|
| Meeting | Invites, updates, cancellations |
| Task/Request | Someone asking you to do something |
| Question | Needs your answer |
| Update/Report | Status updates, progress reports |
| Approval | Needs your sign-off |
| Newsletter | Subscribed content |
| Marketing | Promotional content |
| Alert/Notification | System alerts, notifications |
| Personal | Non-work related |
| Spam/Phishing | Unwanted or suspicious |
| Priority | Response Time | Indicators |
|---|---|---|
| 🔴 Urgent | Within hours | Deadline today, executive request, blocking issue |
| 🟠 High | Within 24h | Important client, time-sensitive, direct request |
| 🟡 Normal | Within week | Standard requests, routine matters |
| 🟢 Low | When convenient | FYI, newsletters, non-urgent updates |
"Classify this email: [paste email content]"
"Classify these emails and organize by priority:
1. [Email 1]
2. [Email 2]
3. [Email 3]"
"Classify my emails. Treat anything from @client.com as high priority"
## Email Classification
**From**: sender@example.com
**Subject**: Q1 Budget Approval Needed
| Attribute | Value |
|-----------|-------|
| **Category** | Action Required |
| **Type** | Approval |
| **Priority** | 🔴 Urgent |
| **Deadline** | EOD Friday |
| **Sender Importance** | High (CFO) |
### Recommended Action
Review attached budget and approve/reject by Friday EOD.
### Suggested Response Time
Within 4 hours
### Labels/Tags
`finance`, `approval`, `q1-budget`, `executive`
## Email Classification Results
**Total Emails**: 15
**Processing Date**: 2026-01-29
### Summary
| Category | Count | % |
|----------|-------|---|
| Action Required | 4 | 27% |
| FYI | 6 | 40% |
| Delete/Spam | 3 | 20% |
| Waiting | 2 | 13% |
### 🔴 Urgent (2)
1. **[Subject]** from [Sender] - [Action needed]
2. **[Subject]** from [Sender] - [Action needed]
### 🟠 High Priority (3)
1. **[Subject]** from [Sender] - [Type]
2. ...
### 🟡 Normal (5)
1. ...
### 🟢 Low/FYI (5)
1. ...
## My Email Rules
### VIP Senders (Always High Priority)
- CEO, CFO, CTO
- Direct manager
- Key clients: @bigclient.com
### Auto-Archive
- Newsletters (unless from [specific])
- Automated reports (after reading)
- CC-only emails (if no @mention)
### Auto-Delegate
- IT support requests → it-team@
- HR questions → hr@
### Red Flags (Mark Urgent)
- "URGENT" in subject
- Legal/compliance mentions
- Customer complaints
## Suspicious Email Indicators
**Risk Level**: 🔴 High / 🟠 Medium / 🟢 Low
### Red Flags Detected
- [ ] Sender domain doesn't match display name
- [ ] Urgency pressure tactics
- [ ] Request for credentials/personal info
- [ ] Suspicious links (hover to check)
- [ ] Unexpected attachments
- [ ] Grammar/spelling errors
- [ ] Generic greeting ("Dear Customer")
### Recommendation
[Do not click links / Report as phishing / Safe to proceed]
## Recommended Processing Order
### Morning (30 min)
1. 🔴 Urgent emails first (2 emails, ~10 min)
2. 🟠 High priority (3 emails, ~15 min)
3. Quick wins under 2 min (5 emails, ~5 min)
### Batch Later
- 🟡 Normal priority - schedule 1 hour block
- 🟢 Newsletters - end of day or weekend
### Delegate Now
- Forward [Email X] to [Person] for handling
📁 Inbox
├── 📁 Action Required
│ ├── 📁 Today
│ ├── 📁 This Week
│ └── 📁 Waiting For Response
├── 📁 FYI / Read
├── 📁 Reference
│ ├── 📁 Projects
│ ├── 📁 Clients
│ └── 📁 Receipts
└── 📁 Newsletters
Weekly Installs
0
Repository
GitHub Stars
5
First Seen
Jan 1, 1970
Security Audits
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
106,200 周安装