local-email-ops

---

name: local-email-ops description: Use this skill for local mailbox workflows: discover configured mailboxes, sync/index each mailbox, triage unread mail, and handle calendar invites using the configured calendar target. disable-model-invocation: true compatibility: Requires notmuch, isync/mbsync, msmtp, jq, and local mailbox access. metadata: author: voicemail version: "1.1" scope: local-email-workflow allowed-tools: Bash Read Edit Write Grep Find

Local Email Operations Skill

Use this skill for reusable, local email operations across one or more mailboxes.

Keep execution workflow-focused and configuration-driven.

Workflow

If anything is missing or not working, check references/config.md first and apply its remediation flow before continuing.

1. Load configured mailboxes

• Read mailbox definitions from configuration (MAILBOXES_FILE) or environment (MAILBOXES).
• Resolve per-mailbox index configuration (NOTMUCH_CONFIG or mailbox-specific config path).

2. For each configured mailbox, run core pipeline

• Sync mailbox (mbsync target or full sync)
• Index updates (notmuch new)
• Triage unread/inbox mail using configured query/rules
• Apply actions (tagging, archiving, mark handled mail as read)

3. Calendar handling (abstract)

• If an invite is detected, create/update an event in the configured calendar target.
• Keep calendar provider details out of this file; use references examples/config.

4. Validate

• Confirm unread/inbox counts and expected tag changes.
• Confirm invite handling actions were applied when enabled.

5. Report

• For each mailbox: sync status, indexed message changes, triage actions, invite actions.

Operating rules

• No hardcoded mailbox IDs, domains, or personal addresses in this skill body.
• No provider-specific setup instructions here.
• Use placeholders in commands and documentation.
• Keep steps imperative and short.

References

• Configuration contract: references/config.md
• Concrete setups: references/examples.md
• Command snippets: references/commands.md

Output requirements

When completing a task, include:

1. Files changed
2. Commands run
3. Validation results
4. Any manual follow-up steps