Generate a personal operating memo from behavioral evidence — calendar patterns, Fathom meeting transcripts, Familiar screen captures, and reflective conversation. Reveals how you actually spend time vs. how you think you spend it. Use when the user says "self insight", "personal insights", "operating memo", "how do I spend my time", "analyze my patterns", "what should I focus on", or during initial Obsidian strategy setup. Re-run quarterly to refresh the memo.
Analyze behavioral data to generate a personal operating memo — a strategic alignment doc that open-week and open-day use for coaching and trap detection.
People are unreliable narrators of their own time. Calendar data, meeting transcripts, and screen captures reveal the truth. This skill synthesizes evidence from multiple sources, surfaces patterns the builder may not see, and facilitates a reflective conversation to turn data into a personal strategy document.
The output is honest, not flattering. If you spend 60% of your time on things you say you don't do, the memo says so.
/open-week opt-in flow)next-review date passes)| Source | What It Reveals | Access |
|---|
| Universal? |
|---|
| Google Calendar | Where time goes: meeting load, partners, recurring commitments, deep work gaps | gcal_list_events MCP (90 days) | Yes — everyone has this |
| Fathom transcripts | How you think: what you advocate for, resist, where you lead vs. follow, coaching themes | Fathom API (90 days) | No — optional |
| Familiar captures | Where attention goes: apps, screen time, tool distribution | Bash: scan $HOME/familiar/stills-markdown/ (7 days) | No — optional |
| Reflective conversation | Self-awareness: what you believe about your role, strengths, traps | Direct dialogue | Yes — always |
Use whatever sources are available. Calendar + conversation is the minimum viable input. Each additional source adds depth.
# Check Fathom — check FATHOM_API_KEY environment variable or .env file
echo "${FATHOM_API_KEY:+FATHOM: available}" || true
[ -z "$FATHOM_API_KEY" ] && grep -q FATHOM_API_KEY .env 2>/dev/null && echo "FATHOM: available (from .env)" || [ -z "$FATHOM_API_KEY" ] && echo "FATHOM: not available"
# Check Familiar
ls $HOME/familiar/stills-markdown/ 2>/dev/null | head -1 && echo "FAMILIAR: available" || echo "FAMILIAR: not available"
Google Calendar is always available via MCP.
Tell the user what data sources are available:
"I can pull from: Google Calendar (90 days), [Fathom transcripts], [Familiar screen captures]. The more sources, the richer the insights. Ready to start?"
2a. Calendar analysis (always)
gcal_list_events(
timeMin="90 days ago",
timeMax="today",
timeZone="America/Denver",
condenseEventDetails=true,
maxResults=250
)
Analyze:
2b. Fathom analysis (if available)
# Fetch 90 days of meetings with summaries
# (Use same pattern as close-day Fathom fetch but with 90-day range)
Analyze summaries and action items for:
2c. Familiar analysis (if available, last 7 days)
# App distribution
grep -h "^app:" $HOME/familiar/stills-markdown/session-*/*.md 2>/dev/null \
| sort | uniq -c | sort -rn
# Chrome breakdown
awk '/^app: Google Chrome/{f=1} f && /^window_title_raw:/{print; f=0}' \
$HOME/familiar/stills-markdown/session-*/*.md 2>/dev/null \
| sort | uniq -c | sort -rn | head -30
Analyze:
Combine all available data into a structured insight report. Present to the user BEFORE writing the operating memo — this is the "here's what the data says" moment.
## Personal Insights Report
### How You Actually Spend Your Time
**Calendar says:**
- [X] meetings/week averaging [Y] hours
- Top recurring: [list top 5 with hours]
- Heaviest day: [day] ([N] meetings). Lightest: [day]
- Deep work windows: [description of consistent gaps, if any]
- Meeting partners (weekly+): [names]
**Fathom says:** (if available)
- Your meetings are mostly about: [top 5 topics]
- You generate [N] action items per meeting — [X] assigned to you
- The word "delegate" appeared [N] times in [M] meetings. "Build" appeared [X] times.
- Coaching themes: [top patterns from coaching sessions]
**Familiar says:** (if available)
- Screen time split: [X]% Slack, [Y]% terminal, [Z]% meetings, [W]% other
- Building vs. managing: [ratio]
- You context-switch approximately [N] times per hour
### The Story the Data Tells
[2-3 sentences synthesizing across all sources. Be direct.]
Example: "Your calendar says you're a manager (15h/week in meetings). Your Fathom transcripts say you want to be an architect (top topic: 'build'). Your screen time confirms you're stuck in the middle — 40% Slack, 20% terminal. The word 'delegate' appeared once in 90 days of meetings."
### Patterns to Watch
1. [Pattern] — [evidence] — [implication]
2. [Pattern] — [evidence] — [implication]
3. [Pattern] — [evidence] — [implication]
### Strengths the Data Confirms
1. [Strength] — [evidence]
2. [Strength] — [evidence]
### Meeting Health
- Target recommended: [X]h/week (based on role)
- Current: [Y]h/week
- Recurring meetings to challenge: [list with rationale]
- Meetings that consistently produce decisions: [list]
- Meetings that don't: [list]
After presenting the data, have a conversation. This is not 5 scripted questions — it's a dialogue guided by what the data revealed.
Start with the headline:
"The data tells an interesting story. [1-2 sentence synthesis]. Does that ring true?"
Then explore based on what the data showed:
For users without rich data (no Fathom, no Familiar): Ask these questions directly, informed by whatever calendar data exists:
From the deep Fathom analysis + calendar patterns + reflective conversation, generate a personal profile at $OBSIDIAN_VAULT_PATH/10-strategy/personal-profile.md. This is the "who you are" companion to the operating memo's "what you do."
Structure (6 sections, each backed by evidence):
# Personal Profile — [Name]
## How I Work Best
Peak performance patterns: time of day, solo vs collaborative, optimal work structure,
energy rhythm. Sourced from calendar gaps analysis + Familiar screen data + meeting
transcript quality patterns.
## What Energizes Me / What Drains Me
Energy audit: what activities produce energy vs. consume it? Inferred from:
- Meeting topics where summaries are longest and most detailed (energy)
- Topics with vague action items that reappear across meetings (drain)
- What you volunteer for vs. what gets assigned to you
- Calendar patterns: what do you schedule yourself vs. get invited to
## My Top Strengths (with evidence)
3-4 observed strengths, each with:
- What it is (2-3 sentences)
- Specific meeting evidence (dates, what happened)
- "When this is at its best" — the ideal application
- "When this becomes a trap" — the strength overplayed
Inference methods:
- What topics pull you into meetings you weren't invited to
- What questions people bring to YOU specifically
- Moments where group energy shifts after you speak
- What you do in unstructured time (Familiar data)
- Reflected Best Self moments from transcripts
## My Top Traps (strengths overplayed)
2-3 derailers, each with:
- The pattern described plainly
- Specific evidence (meetings, dates, frequency)
- The cost of this pattern (what gets delayed or missed)
Look for: coaching themes that repeat, things you do even when it's not helping,
gaps between stated priorities and actual time allocation.
## What I Actually Value
Inferred from 90 days of meetings:
- What do you consistently push back on? What hills do you die on?
- What do you advocate for when it costs political capital?
- Repeated phrases and themes across meetings
- What you NEVER bring up (the dog that doesn't bark)
## Working Genius Profile (inferred)
Map observable meeting behavior to Lencioni's 6 types:
- Wonder: asks "why" and "what if," reframes problems at higher level
- Invention: generates novel solutions, connects disparate ideas
- Discernment: gut-checks proposals, says "that won't work because..."
- Galvanizing: rallies people, assigns next steps, sets vision
- Enablement: volunteers to help, asks "what do you need?"
- Tenacity: follows up on past items, tracks completion, handles details
Rank as primary / strong / moderate / weaker / weakest based on transcript evidence.
This is directional, not a formal assessment — label it as "inferred from meeting behavior."
For users without Fathom: The profile is lighter but still useful. Calendar patterns provide "How I Work Best" and partial "Energy" data. The reflective conversation fills "Strengths," "Traps," and "Values." Skip Working Genius without transcript data — it requires behavioral evidence.
From the data + conversation, generate the operating memo:
---