---
name: digital-twin
description: Build a private "digital twin" of the user — a rich profile of their voice, relationships, routines, and priorities — by reading across their own Mac apps (Mail, Messages, Calendar, Contacts, Notes) with LMCP. Everything stays on the Mac. Triggers on "build my digital twin / make an AI version of me / learn my style / who am I from my data".
license: free
homepage: https://local-mcp.com
---

# Digital Twin

Builds a **digital twin** of the user — a structured, reusable profile of how they write, who they
talk to, how their week runs, what they're working on, and what they care about — synthesized from
their OWN data through LMCP. Nothing is uploaded: every source is read locally on the user's Mac,
and the twin is written to a file on that Mac. This is the privacy-first alternative to cloud
"clone yourself" services that ingest your data.

## When to use this skill

The user asks to "build my digital twin", "make an AI version of me", "learn how I write / my
style", "create a profile of me from my data", or "so my assistant knows who I am".

## Preflight (do this first)

1. Call `lmcp_state` / `run_diagnostics` to see which sources are connected (Mail, Messages,
   Calendar, Contacts, Notes, Reminders, Teams, Files). Build from what's available — never block on
   a missing one.
2. Tell the user, in one line, what you'll read and that **it all stays on their Mac**. Proceed
   unless they object.

## Playbook

Sample breadth over depth — enough to find patterns, not every item.

1. **Voice (the most important signal): read SENT items.** `search_emails` / `list_emails` on the
   Sent mailbox and the user's own `list_messages` / `read_messages` — this is how they actually
   write (greetings, sign-offs, length, formality, emoji, languages).
2. **Relationships.** From Contacts + who they email/message most: the inner circle, work vs personal,
   how they address different people.
3. **Rhythm.** `list_calendar_events` (recurring meetings, working hours, focus blocks) +
   `list_reminders` — the shape of a typical week and how they manage commitments.
4. **Themes & projects.** Recurring subjects across mail/notes/reminders — what they're building,
   deciding, worrying about.
5. **Values & tone.** How they handle asks, say no, give praise, escalate — the through-line.

## Produce the twin

Write a single **Digital Twin** document (a note via `create_note`, or a Markdown file) with clear
sections: *Voice & style · Key relationships · Weekly rhythm · Active themes · Values & tone*, each
grounded in concrete observations (with light examples, never raw dumps). Close with **"How to use
me": draft in my voice, reply as me, brief a new assistant, prep me for my day.** Offer those as
immediate next actions.

## Guardrails (non-negotiable)

- **Local only.** Never send the user's personal data to any external service. The twin lives on
  the user's Mac.
- **Observe, don't invent.** Every trait is grounded in what the data shows — no fabricated bio.
- **Sensitive content stays summarized.** Characterize patterns; don't reproduce private messages
  verbatim in the profile.
- **The user owns it.** Offer to update the twin later as new data accumulates, and to delete it.

## Next step

Offer to put the twin to work now — draft an email in their voice, summarize "who am I" for a new
assistant, or generate a morning brief written the way they'd write it.
