Coding

remember-emails

Tracks email threads, promised actions, and follow-ups so nothing falls through the cracks. Use when an agent manages correspondence and needs to know what was promised, to whom, and by when. Requires a BlueColumn API key (bc_live_*).

What it does

The skill document

Remember Emails — BlueColumn Skill

Email threads have a memory of their own — promises, deadlines, and loose ends. This skill records the state of every important thread so the agent knows what is pending without re-reading the inbox.

Log the thread state

After any meaningful exchange, store who promised what and the deadline.

curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-remember \
  -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "THREAD: with Sarah Kim re: vendor contract. We promised revised pricing sheet by Aug 5. She owes us the signed NDA. Last message: hers, Jul 30.", "title": "email - vendor contract"}'

Follow-up radar

Before starting the day's email, ask what is pending and overdue.

curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-recall \
  -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q": "Which email threads have open promises or deadlines this week?"}'

Draft from context

When drafting a follow-up, pull the thread state so the message references the real last touchpoint.

curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-recall \
  -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q": "What was the last exchange with Sarah Kim about the vendor contract?"}'

Email workflow

On send — store what was promised and by when.
Daily — recall open promises; flag anything overdue or due this week.
On reply — pull the thread state first, then draft with the real context.
On resolution — close the thread by storing the outcome, so it stops resurfacing.

Tag for filtering

curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-note \
  -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "Follow up with Sarah Kim on Aug 5 — pricing sheet due.", "tags": ["email", "follow-up"]}'

Docs

API reference: https://bluecolumn.ai/docs — fields are text, q, tags (not content/query/note).

Related skills

gmail-memory

Give AI agents Remember Gmail threads. using BlueColumn persistent memory. Use when an agent manages email and needs thread history; when the user wants to store, recall, or search gmail memory context. Requires a BlueColumn API key (bc_live_*).

remember-invoices

Billing memory that tracks invoices, payment status, and follow-ups so revenue is never lost in a thread. Use when an agent handles billing, chases payments, or answers "what is outstanding". Requires a BlueColumn API key (bc_live_*).

remember-customer-names

Never blank on a customer again — names, roles, companies, and the details that make conversations personal. Use when an agent talks to customers and should address them correctly and remember their context. Requires a BlueColumn API key (bc_live_*).

remember-projects

A project memory that tracks status, milestones, owners, and blockers so nothing stalls silently. Use when an agent manages ongoing work and needs a live picture of every project. Requires a BlueColumn API key (bc_live_*).

remember-medical-notes

Private, authorized health-appointment memory for care continuity. Use when an agent tracks appointments, symptoms, and provider instructions for an authorized user, with consent and confidentiality built in. Requires a BlueColumn API key (bc_live_*).

content-memory

Give AI agents Remember content ideas and drafts. using BlueColumn persistent memory. Use when an agent supports content creation and needs idea continuity; when the user wants to store, recall, or search content memory context. Requires a BlueColumn API key (bc_live_*).