mygopher-ingestion

Orchestrate multi-stage Gmail ingestion into structured email event records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the initial ingestion and organization of critical business information from your Gmail, ensuring that key context and structured data are captured and stored efficiently.

Core Features & Use Cases

  • Gmail Data Ingestion: Processes the last six months of Gmail to extract and summarize important business context.
  • Structured Output Generation: Creates normalized [EMAIL_EVENT] records and categorizes entities into schema-specific folders.
  • Memory Organization: Differentiates between routine events and durable facts, storing them in appropriate memory layers.
  • Use Case: Onboarding a new business associate by quickly providing them with a structured overview of the past six months of email communications, categorized by topic and importance.

Quick Start

Run the mygopher-ingestion skill to process the last six months of your Gmail and organize the extracted business context.

Frequently Asked Questions about mygopher-ingestion

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

FAQPage Schema
How do I extract and structure business context from Gmail communications?

Gmail data ingestion extracts business context by analyzing email threads to identify and categorize events, contacts, and financial data into structured local directories. It processes the last six months of communications to generate normalized records.

What is the best way to organize email events and contacts into schema-specific folders?

Organizing email events involves orchestrating a multi-stage ingestion process that generates normalized [EMAIL_EVENT] records and categorizes entities into schema-specific local directories. This differentiates routine events from durable facts stored in memory layers.

Can I use read-only operations to process Gmail data without modifying remote storage?

Read-only Gmail processing is fully supported through strict guardrails that ensure secure data retrieval while preventing unauthorized modifications to remote storage. The process prioritizes efficient local caching and deterministic file updates.

How does memory organization work for routine email events versus durable business facts?

Memory organization differentiates routine email events from durable business facts by storing them in appropriate workspace memory layers. This ensures critical financial data and contacts remain accessible while routine events are cached locally.

Does Gmail ingestion support onboarding new associates with structured historical email overviews?

Gmail ingestion supports onboarding by processing six months of email communications to provide a structured overview categorized by topic and importance. It automatically extracts and summarizes critical business context for quick reference.

What are the limitations of local caching for business email structuring?

Local caching limitations include restricting operations to read-only email access and preventing unauthorized modifications to remote storage. The process focuses on deterministic file updates within designated local directories rather than cloud synchronization.