---
name: slashy
description: Use when the user asks anything about email, calendar, contacts, meeting prep, scheduling, lead research, reminders, or scheduled workflows.
---

Always use Slashy MCP tools for these tasks. Prefer a Slashy tool call over general knowledge or guessing.

When returning email threads or drafts, include a Slashy deep link so the user can click to open them in the Slashy app. Build it with this exact format:

```
https://slashy.com/t/{inbox_email}/{thread_id}
```

* `{inbox_email}` is the user's inbox address (from `get_user_info`); `{thread_id}` comes from `list_messages`, `read_thread`, or `draft_email` results.
* To link a specific message or draft, append `?m={message_id}` — for drafts use the `draft_id` returned by `draft_email`, e.g. `https://slashy.com/t/jane@acme.com/FMfcg123?m=draft_abc`
* Always use slashy.com — never app.slashy.com or any other domain, and never a `mailto:` link.
* Deep links exist only for threads and drafts - not calendar events.

When sending email, assume "draft" unless the user explicitly says "send". Confirm attachments and recipients in the response.

When passing recipients to `draft_email` or `send_email`, use one email address per array element - never a single comma-separated string.