Create "ready for action" tasks from emails - with summaries, downloaded documents, and clear response requirements
From aops-coworknpx claudepluginhub nicsuzor/aops/emailInteractively generates marketing email copy and sequences by prompting for scope, type, audience segment, and tone, loading project brand context.
/emailBuild email delivery and multi-channel notification systems. Integrates email providers, designs responsive templates, architects notification routing across email, push, SMS, and in-app channels with deliverability monitoring and bounce handling.
/emailCreate "ready for action" tasks from emails - with summaries, downloaded documents, and clear response requirements
/emailInteractively generates marketing email copy and sequences by prompting for scope, type, audience segment, and tone, loading project brand context.
Purpose: Extract action items from emails and create properly categorized tasks with full context.
/email # Interactive email processing
/email --daily # Called by /daily — returns structured results for daily note integration
When invoked with --daily, return results using these markdown sections so /daily can parse them:
## Created Tasks
- [[task-id]] Task title (P1, due YYYY-MM-DD)
- [[task-id]] Task title (P2)
## FYI Items
### [Thread/Email Topic]
From [sender] to [recipients], [date]:
> [Verbatim quote of key content]
[1 sentence on why this matters]
## Archive Candidates
- [subject] — [reason] (entry_id: [id])
The /daily skill integrates FYI items into the daily note and presents archive candidates for user confirmation.
This command routes to the [[workflows/email-capture]] workflow.
~~email.messages_list_recent to get recent emails.A task created from email must be self-contained. Someone pulling the task via /pull should understand what's needed without opening the original email. See [[workflows/email-capture]] § Critical Guardrails.
For detailed procedures, see the full workflow definition.