pa-email

Process unread emails into TODOs, replies, and archived messages via MCP tools.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/christophevg/c3 --skill pa-email
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pa-email
Source: https://github.com/christophevg/c3/tree/main/skills/pa-email
Command: npx skills add https://github.com/christophevg/c3 --skill pa-email

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pa-email eliminates the manual effort of checking an inbox, extracting actionable items, replying to senders, and archiving processed messages, so work can move forward faster.

Core Features & Use Cases

  • Inbox polling and processing: Uses the MCP email server to search for unread messages, fetch content, and process each email in a controlled workflow.
  • Actionable extraction and routing: Categorizes items into project TODOs, questions for clarification, cross-cutting agent-level TODOs, and information/memory updates.
  • Reply + archive loop: Generates an appropriate reply via MCP, then marks the email as read and moves it to the Archive to keep the inbox clean.
  • Guardrails for safe email operations: Enforces “tools-only” email handling through MCP tools (no direct IMAP/HTTP/email scraping).

Quick Start

Use pa-email when you want to process new unread messages and automatically reply, create TODOs, and archive them from your inbox.

Frequently Asked Questions about pa-email

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate unread email processing into actionable TODOs?

Automating unread email processing requires polling an inbox for unseen messages, fetching content, categorizing items into project TODOs, generating replies, and moving messages to an archive. This workflow eliminates manual inbox triage by routing actionable items directly into an agentic task system.

Does pa-email require MCP tools for inbox automation?

Yes, pa-email requires MCP email tools for inbox automation. It enforces a tools-only approach to email handling, using MCP specifically to list accounts, search unseen messages, fetch content, send replies, and move items to the archive.

How does agentic email categorization and project routing work?

Agentic email categorization works by processing unread messages and routing them into specific buckets: project TODOs, clarification questions, cross-cutting agent-level TODOs, and memory updates. This ensures every unread email is triaged into a structured, actionable format.

What is the best way to reply and archive emails in an automated workflow?

The best way to reply and archive emails in an automated workflow is using a reply and archive loop. The system generates an appropriate reply via MCP tools, marks the email as read, and moves it to the Archive folder to maintain a clean inbox.

Can I use direct IMAP connections for email scraping with this workflow?

No, you cannot use direct IMAP or HTTP connections for email scraping with this workflow. It enforces guardrails for safe email operations by requiring tools-only handling through MCP email tools, preventing direct protocol access.

Why does automated email processing use MCP tool IDs instead of RFC Message-IDs?

Automated email processing uses MCP tool IDs instead of RFC Message-IDs to safely mark messages as read and move them to the archive. The MCP tool ID ensures accurate folder routing within the email server compared to standard message identifiers.