<< All versions
Skill v1.0.1
currentAutomated scan100/100quixiai/hexis/email-digest
2 files
──Details
PublishedJune 7, 2026 at 05:17 AM
Content Hashsha256:d1b51c7ba98c5641...
Git SHA4948ea6119a7
Bump Typepatch
──Files
Files (1 file, 2.5 KB)
SKILL.md2.5 KBactive
SKILL.md · 42 lines · 2.5 KB
version: "1.0.1" name: email-digest description: Digest and ingest emails into memory, surfacing important threads and action items category: communication requires: tools: [list_emails, read_email, remember, recall] config: [gmail] env: [GOOGLE_CREDENTIALS_JSON] contexts: [heartbeat] bound_tools: [list_emails, read_email, search_emails, ingest_emails]
Email Digest Workflow
Process incoming emails into structured memories, extract action items, and surface threads that need attention.
When to Use
- During autonomous heartbeats to check for new mail since the last digest
- When the user asks "what's in my inbox" or "any important emails"
- When a goal depends on information that may have arrived via email
- When preparing a daily briefing that includes email highlights
Step-by-Step Methodology
- Check recency: Use
recallto find when the last email digest ran. Avoid re-processing messages already ingested. - List new emails: Call
list_emailswith a date filter to fetch unread or recent messages. Start with the inbox; expand to other labels only if the user has configured them. - Triage by sender and subject: Scan the list for high-signal indicators -- known contacts, reply chains the user is on, calendar invites, and keywords matching active goals.
- Read priority threads: Use
read_emailon the top 5-10 most relevant messages. Do not read every email; batch processing wastes energy and context. - Extract action items: For each important email, identify: (a) what is being asked, (b) who is asking, (c) any deadline mentioned, (d) whether a reply is expected.
- Store findings: Use
rememberto persist action items as episodic memories with high importance. Tag with the sender, thread ID, and any relevant goal. - Surface urgency: If an email requires a time-sensitive response, flag it in the heartbeat result so it can be raised to the user at next opportunity.
Quality Guidelines
- Never store raw email bodies as memories. Summarize and extract the salient points.
- Respect privacy: do not log email content to external services. All storage stays in the local Postgres brain.
- When multiple emails belong to the same thread, consolidate into a single memory rather than creating duplicates.
- If credentials are missing or expired, fail gracefully and note the issue rather than retrying in a loop.
- Prefer recalling existing contact memories to enrich email context (who is this person, what is the relationship).