AaronRoeF

Exo Mesh — Development skill for Claude Code

Development community

See the whole relationship, not the fragment one inbox remembers.

How to install Exo Mesh

This entry records only its repository, not the path inside it, so there is no exact command to give. Open AaronRoeF/exo-mesh and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Exo Mesh does

See the whole relationship, not the fragment one inbox remembers. Mail, calendar, iMessage and contacts joined locally into one record per person — for you and every agent you build.

Alternatives in Development

Domxss — Confirm DOM XSS in a real headless browser — injects canary payloads into params + URL fragment and only repor 4.5k ★
Checkup Calendar — 复查日历生成 348 ★
Module 18 Calendar.En — Module 18 Lesson 4-2 — Assist Calendar (calendar_ops / gog calendar) via prompts 347 ★

README

exo-mesh

**Walk into every conversation with the whole relationship in front of you, not the fragment one inbox remembers.**

Four systems each hold a quarter of every relationship you have, and nothing joins them. So the questions you actually ask — when did I last talk to this person, what are our open items, where did we leave off — cost four searches and a guess.

exo-mesh answers them in one local read. It mirrors your Gmail into a [notmuch](https://notmuchmail.org/)-indexed Maildir, pulls your calendars, takes a read-only snapshot of iMessage, merges your contacts, and resolves the whole pile into a **mesh**: one row per person, carrying every address and number they own, per-channel recency, who usually starts the conversation, and how many years it's run.

Everything stays on your disk. No service, no daemon, no API key on the query path. Your relationship history is the most revealing corpus you own, and this is the copy that answers in single-digit milliseconds without renting it to anyone.

And it's the store an agent can read. `exo-mail mcp` speaks MCP, so every agent, skill and draft you build reasons over the whole relationship instead of one inbox's fragment, from a file on your disk under a retention policy you wrote. It runs against a six-figure message archive, not a demo fixture.

Four channels. One person. Zero egress.

![Four channels in, one person out: mail, calendar, iMessage and contacts are pulled into local replicas, resolved by email, phone and name into a mesh holding one row per person, which the CLI and MCP server read — nothing leaves the machine.](assets/exo-mesh.svg)

IMPORTANT NOTE ON GOVERNANCE AND SECURITY

I'm leaving out big parts of my implementation because I'm not interested in disclosing all the specifics of my security and governance setup. You can see parts of what I'm doing here: agentrust-io.com if you're interested. And generally assume this is a project I'm sharing, not a product. I hope you get value. Enjo