Email

2. Verify permissions

Before calling the provider tool, verify that every required operation is included in allowedOperations. If any is missing:

This action requires the "<operation>" permission, which is not currently enabled.
Please enable it in the Email skill settings and try again.

3. Gather context

Use search or list to locate the relevant messages before composing or acting. Always prefer targeted queries (sender, subject, date range) over fetching the full inbox.

4. Act & confirm

• For read / search: execute immediately and present results using summaryStyle.
• For send / reply / draft: draft the content first, present it to the user for review (if confirmBeforeSend is true), then submit.
• For move / label / delete: state the scope of the change ("12 messages will be archived") before executing.
• For templates: list existing templates before creating a new one to avoid duplicates.

5. Summarise

After completing all actions, produce a brief plain-language summary:

Summary:
- Read 8 unread messages from the last 24 hours.
- Found 2 messages from Alice requiring a reply.
- Drafted reply to Alice's "Project Kickoff" thread — awaiting your approval.

Next steps:
- Approve or edit the draft reply.
- Review the 3 promotional emails flagged for archiving.

Output Format

Goal: <what was requested>

Actions taken:
1. <action> — <outcome>
2. <action> — <outcome>

Summary:
<plain-language summary>

Next steps:
- <item>

Guidelines

• Limit fetched messages to maxMessagesToRead per operation.
• When summarising messages, include: sender, date, subject, and a one-sentence synopsis. Never output full message bodies unless explicitly requested.
• If the provider tool returns an auth error, instruct the user to re-authenticate rather than retrying automatically.
• Treat all email addresses and message contents as sensitive PII.
• Do not infer or guess email addresses — always retrieve them from the message data.