email-organizer

Process structured email events to update daily logs and durable memory.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/StevenMih/amicable --skill email-organizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-organizer
Source: https://github.com/StevenMih/amicable/tree/main/deploy/mygopher/skills/email-organizer
Command: npx skills add https://github.com/StevenMih/amicable --skill email-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the organization of email communications by processing events, updating logs, and storing key information in durable memory and structured schemas.

Core Features & Use Cases

  • Event Consumption: Processes structured email events (e.g., draft created, reply received).
  • Memory Management: Updates daily logs and durable memory with relevant facts and summaries.
  • Schema Alignment: Maps extracted information into predefined business schemas for projects, contacts, and finances.
  • Use Case: Automatically log a new client contact and their project details when an email thread indicates a new engagement.

Quick Start

Process the latest email event to update memory and logs.

Frequently Asked Questions about email-organizer

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

FAQPage Schema
How do I automate email organization into structured logs and memory?

Automating email organization involves processing structured email events to update daily logs and durable memory, writing schema-aligned artifacts to designated locations. You need an external email event emitter to trigger the incremental state updates.

Can I automatically map extracted email data into predefined business schemas for projects and contacts?

Yes, schema alignment maps extracted email information into predefined business schemas for projects, contacts, and finances. When an email thread indicates a new engagement, it automatically logs the new client contact and project details.

How does an observer-writer contract work for email event consumption?

An observer-writer contract requires external email event emitters to send structured events like draft created or reply received. The system observes these events to update memory and logs while enforcing guardrails against unauthorized actions.

Do I need an external email event emitter to process email communications?

Yes, you need integration with external email event emitters to process email communications. The system requires these emitters to send structured events and adherence to a defined observer-writer contract to manage incremental organization state safely.

What are the limitations of using automated schema alignment for email logging?

Limitations include strict adherence to a defined observer-writer contract and dependency on external email event emitters. Guardrails against unauthorized actions restrict processing outside predefined business schemas, requiring structured event formats to function correctly.

What's the best way to manage incremental organization state for email events?

Managing incremental organization state requires observing structured email events to update daily logs and durable memory. The system writes schema-aligned artifacts to designated locations, maintaining state while enforcing guardrails against unauthorized actions.