How do I install the Mailwise skill?

Run npx skillmds@latest add dvcrn/mailwise in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mailwise safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mailwise?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mailwise free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mailwise?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mailwise by dvcrn — Agent Skill

Name: Mailwise
Rating: 4.5 (4 reviews)
Author: dvcrn

Mailwise

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".

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

MailWise — Email Issue Knowledge Base

Search and analyze your team's email issue threads. MailWise indexes EML files, tags expert engineers' replies, and uses RAG to help you learn from how experienced engineers investigated and resolved past issues.

When to use this skill

User asks about similar past issues or bugs
User wants to know how an issue was resolved before
User pastes a bug report and wants analysis based on team history
User asks about root cause patterns or debugging approaches
User wants to find what expert engineers said about a topic

Commands

Search for similar issues

Find past issues matching a description. Returns ranked results with expert tags.

mailwise search "describe the issue here" --show-body

Options:

--show-body — show a preview of each matching message
--expert-only — only show replies from expert engineers
-k N — number of results (default: 10)

Example:

mailwise search "email sync failure after folder migration" --show-body
mailwise search "calendar not updating on Mac" --expert-only -k 5

Deep analysis with RAG

Retrieve similar past issues and ask Claude to synthesize expert insights, root cause patterns, and debugging approaches.

mailwise analyze "paste full bug report or issue description here"

Options:

-k N — number of similar issues to feed to Claude (default: 5, increase for broader analysis)

Tip: For best results, paste the FULL bug report content, not just a title. More context (error codes, logs, environment details) produces better matches.

Example:

mailwise analyze "User on Mac Outlook moves emails from Inbox to local folder. Emails disappear but reappear after 30 minutes. No DeleteMessage in HxLogs."
mailwise analyze "$(cat bug_report.txt)" -k 10

View a full email thread

After finding an issue via search, view the complete parsed thread with all replies and expert tags.

mailwise show <EMAIL_ID>

Check index status

mailwise stats

Shows: total indexed emails, thread messages, expert messages, expert coverage percentage.

Index new emails

When the user adds new EML files or wants to refresh the index:

mailwise index

This is incremental — only processes new or changed files. Safe to run repeatedly.

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

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

Setup requirements

Before first use, the user needs to:

Install MailWise:

pip install git+https://github.com/PetrGuan/MailWise.git

Clone the repo for config files:

git clone https://github.com/PetrGuan/MailWise.git && cd MailWise
cp config.example.yaml config.yaml

Edit config.yaml: set eml_directory and add expert engineers
Put .eml files in the configured directory
Run mailwise index to build the initial index

Important notes

All indexing and search runs locally (no data sent to external APIs)
The analyze command requires Claude Code to be installed and authenticated
The index is stored in a local SQLite database
Markdown versions of all parsed threads are written to the markdown/ directory

---name: mailwisedescription: 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".---# MailWise — Email Issue Knowledge BaseSearch and analyze your team's email issue threads. MailWise indexes EML files, tags expert engineers' replies, and uses RAG to help you learn from how experienced engineers investigated and resolved past issues.## When to use this skill- User asks about **similar past issues** or bugs- User wants to know **how an issue was resolved before**- User pastes a **bug report** and wants analysis based on team history- User asks about **root cause patterns** or debugging approaches- User wants to find what **expert engineers** said about a topic## Commands### Search for similar issuesFind past issues matching a description. Returns ranked results with expert tags.```bashmailwise search "describe the issue here" --show-body```Options:- `--show-body` — show a preview of each matching message- `--expert-only` — only show replies from expert engineers- `-k N` — number of results (default: 10)Example:```bashmailwise search "email sync failure after folder migration" --show-bodymailwise search "calendar not updating on Mac" --expert-only -k 5```### Deep analysis with RAGRetrieve similar past issues and ask Claude to synthesize expert insights, root cause patterns, and debugging approaches.```bashmailwise analyze "paste full bug report or issue description here"```Options:- `-k N` — number of similar issues to feed to Claude (default: 5, increase for broader analysis)**Tip:** For best results, paste the FULL bug report content, not just a title. More context (error codes, logs, environment details) produces better matches.Example:```bashmailwise analyze "User on Mac Outlook moves emails from Inbox to local folder. Emails disappear but reappear after 30 minutes. No DeleteMessage in HxLogs."mailwise analyze "$(cat bug_report.txt)" -k 10```### View a full email threadAfter finding an issue via search, view the complete parsed thread with all replies and expert tags.```bashmailwise show <EMAIL_ID>```### Check index status```bashmailwise stats```Shows: total indexed emails, thread messages, expert messages, expert coverage percentage.### Index new emailsWhen the user adds new EML files or wants to refresh the index:```bashmailwise index```This is incremental — only processes new or changed files. Safe to run repeatedly.### Manage expert engineers```bashmailwise experts listmailwise 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 workflow1. User describes an issue or pastes a bug report2. Run `mailwise search "..." --show-body` to find similar past issues3. If promising results found, run `mailwise analyze "..."` for deep RAG analysis4. Use `mailwise show <ID>` to read full threads of interest5. Summarize findings: root cause patterns, debugging steps, and next actions## Setup requirementsBefore first use, the user needs to:1. Install MailWise: ```bash pip install git+https://github.com/PetrGuan/MailWise.git ```2. Clone the repo for config files: ```bash git clone https://github.com/PetrGuan/MailWise.git && cd MailWise cp config.example.yaml config.yaml ```3. Edit `config.yaml`: set `eml_directory` and add expert engineers4. Put `.eml` files in the configured directory5. Run `mailwise index` to build the initial index## Important notes- All indexing and search runs locally (no data sent to external APIs)- The `analyze` command requires Claude Code to be installed and authenticated- The index is stored in a local SQLite database- Markdown versions of all parsed threads are written to the `markdown/` directory

Frequently asked questions