Token导航 LogoToken导航

Agent Skill · 研究检索

mailwise(mailwise 搜索)

mailwise 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

mailwise 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 13,801。

总安装 9,082周安装 371GitHub Stars 1下载 2,909核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.2

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mailwise(mailwise 搜索)
来源仓库:https://github.com/petrguan/mailwise
安装命令:
openclaw skills install mailwise
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install mailwise

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

从本地知识库检索历史邮件线索,辅助排查技术问题与事件复盘。适合工程师回顾过往故障、查找解决方案或追溯责任记录。基于语义匹配返回相关邮件片段,减少人工翻阅时间。依赖预先构建的知识库质量,结果准确性受索引完整性影响。mailwise 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install mailwise;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

mailwise 怎么安装?

在终端执行 openclaw skills install mailwise。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

mailwise 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

mailwise 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

mailwise 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

mailwise 用的人多吗?

公开数据是累计安装 9,082 次,近一周安装 371 次,下载 2,909 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

mailwise 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
mailwise

mailwise 搜索 · 本页

9,0821接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
mailwise
description
Search and analyze email issue threads from a local knowledge base. Use when the user asks about past bugs, incidents, or wants to find how experienced engineers solved similar issues. Triggers on questions like "have we seen this before", "similar issues", "how did we fix", "root cause analysis", "past incidents".
homepage
https://github.com/PetrGuan/MailWise
user-invocable
true
metadata
{ "openclaw": { "emoji": "📧", "requires": { "bins": ["mailwise", "claude"], "env": { "ANTHROPIC_API_KEY": { "description": "Anthropic API key (only needed for the 'analyze' command; alternative: authenticate via 'claude' CLI login)", "required": false } } }, "install": [{ "id": "pip", "kind": "uv", "package": "mailwise", "bins": ["mailwise"], "label": "Install MailWise from PyPI" }] } }

MailWise — Your Team's Email Memory

Stop re-investigating issues your team already solved. MailWise turns your email threads into a searchable knowledge base — index thousands of EML files locally, tag expert engineers, and use RAG to instantly surface how similar issues were debugged and resolved in the past.

"Have we seen this before?" → MailWise searches 25,000+ emails in under a second and shows you exactly what your best engineers said about it.

What you get

Semantic search — not keyword matching, but meaning-based retrieval across your entire email archive:

$ mailwise search "calendar sync fails after folder migration" --show-body

  #1 [0.89] ★Expert  RE: Outlook calendar not syncing after mailbox move
     From: senior.engineer@example.com (2024-11-15)
     "The root cause is a stale folder-id cache. Clear HxCalendarSync
      and restart the sync service..."

  #2 [0.84]          RE: Sync failure post-migration — Mac clients
     From: support.lead@example.com (2024-10-22)
     "We've seen this pattern before. Check if the migration tool
      preserved the folder GUIDs..."

  #3 [0.81] ★Expert  RE: Calendar items disappearing after move
     From: senior.engineer@example.com (2024-09-08)
     "This is the same class of bug as CASE-4521. The fix is..."

RAG-powered analysis — Claude reads the most relevant past threads and synthesizes debugging guidance:

$ mailwise analyze "User reports calendar events vanish after moving to a new folder"

  Based on 5 similar past issues, here's what your team has found:
  ● Root cause pattern: stale folder-id cache after migration (3 of 5 cases)
  ● Recommended first step: check HxCalendarSync logs for GUID mismatch
  ● Expert consensus: clearing the sync cache resolves ~80% of these cases
  ● Edge case: if GUIDs were not preserved during migration, a full re-sync is needed

Get started in 3 steps

pip install mailwise        # 1. Install from PyPI
mailwise init               # 2. Interactive setup wizard — creates config, sets directories
mailwise index              # 3. Index your EML files (incremental, safe to re-run)

That's it. Now search with mailwise search "..." or get AI analysis with mailwise analyze "...".

Commands

Search for similar issues

mailwise search "describe the issue here" --show-body
  • --show-body — show a preview of each matching message
  • --expert-only — only show replies from expert engineers
  • -k N — number of results (default: 10)

Deep analysis with RAG

mailwise analyze "paste full bug report or issue description here"
  • -k N — number of similar issues to feed to Claude (default: 5)

Tip: Paste the FULL bug report — error codes, logs, environment details produce much better matches.

mailwise analyze "$(cat bug_report.txt)" -k 10

View a full email thread

mailwise show <EMAIL_ID>

Check index status

mailwise stats

Manage expert engineers

mailwise experts list
mailwise experts add engineer@company.com --name "Jane Doe"
mailwise experts remove engineer@company.com

Expert engineers' replies get ★Expert tags and boosted scores in search results.

Typical workflow

  1. User describes an issue or pastes a bug report
  2. Run mailwise search "..." --show-body to find similar past issues
  3. If promising results found, run mailwise analyze "..." for deep RAG analysis
  4. Use mailwise show <ID> to read full threads of interest
  5. Summarize findings: root cause patterns, debugging steps, and next actions

Privacy & data handling

  • Local-only commands (index, search, show, stats, experts): Everything runs on your machine. Embeddings generated locally via sentence-transformers. No data sent anywhere.
  • External LLM command (analyze): Sends email excerpts to the Anthropic API via Claude Code CLI. Do not use on sensitive emails unless your org's data policy permits it.

Authentication

  • The analyze command requires Claude Code CLI — run claude once to authenticate, or set ANTHROPIC_API_KEY
  • No auth needed for local commands (index, search, show, stats, experts)

平台分布

OpenClaw

79.06%
按下载量换算2,300

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills