Connection Profile Format

Integration profiles capture how the user uses a service. All profiles written to Connection Profiles should follow this structure.

Required Header

Every profile must start with a timestamp:

# [Service] Profile

Last analyzed: 2024-01-15T10:30:00Z

Core Sections

Key Contacts / Collaborators

Who the user interacts with most. Prioritize bidirectional relationships — mutual engagement is stronger than one-way contact.

• Include: People with back-and-forth interaction
• Exclude: One-way contacts (newsletters, single outreach)
• Format: Names with brief context about the relationship

Usage Patterns

How the user engages with the service. Integration-specific but always descriptive:

• Busiest days/times
• Preferred labels, channels, or folders
• Common topics or themes

Quick Access

IDs and references for programmatic access in future tasks:

• Thread/message IDs for important conversations
• Channel/database/page IDs
• Any identifiers needed to quickly retrieve content

Style Guidelines

Describe patterns, not statistics. Avoid raw counts and metrics.

Bad	Good
"847 messages sent"	"Heavy Slack user, especially in #engineering"
"12 emails from Sarah"	"Sarah is your most active email contact"
"3.2 meetings/day average"	"Your calendar is meeting-heavy, especially Thursdays"

Focus on actionable context. The profile helps future tasks understand the user's relationship with the service.

Example Structure

# Gmail Profile

Last analyzed: 2024-01-15T10:30:00Z

## Key Contacts

- **Sarah Chen** — Your most active correspondent, mutual back-and-forth
- **Mike Johnson** — Regular but less frequent, mostly project updates

## Email Patterns

Busiest day: Monday
Active labels: Work, Personal, Receipts
Communication style: Quick responses, informal tone

## Quick Access

Recent important threads:
- 18abc123... (Project kickoff with Sarah)
- 17def456... (Budget discussion)