GitHub stars
5

Install

/plugin install office-admin@office.harper.dev

Run it inside Claude Code after adding the marketplace with /plugin marketplace add harperreed/office-admin-claude.

Contents

Discovered from source

Skills 4

Calendar Management with Office Admin

When to Use This Skill

Use this skill when:

  • Adding events from emails
  • Checking for scheduling conflicts
  • Creating calendar holds for tentative events
  • Converting timezones for international contacts
  • Managing working hours and availability
  • Blocking focus time or recurring events

User Calendar Preferences

Load preferences from ~/.claude/office-admin-config.json:

{
  "personal": {
    "timezone": "America/Chicago",
    "workingHours": {
      "start": "09:30",
      "end": "16:30",
      "lunchStart": "12:00",
      "lunchEnd": "13:30"
    }
  },
  "calendar": {
    "defaultDuration": 30,
    "bufferMinutes": 15,
    "schedulingLink": "https://user.cal.com/schedule",
    "autoAddFromEmail": true,
    "eventNaming": {
      "includeLocation": true,
      "includeAttendees": false
    }
  }
}

Core Principles

  1. Always check conflicts first - Before committing to an event
  2. Respect working hours - Use user's configured schedule
  3. Handle timezones carefully - Convert accurately, show both zones
  4. Be proactive - Auto-add events from emails when configured
  5. Use descriptive titles - Include location/context per user preference

Adding Events from Emails

Step 1: Extract Event Details

Look for in the email:

  • Date and time (or phrases like "tomorrow", "next Tuesday", "in two weeks")
  • Duration (or use defaultDuration from config)
  • Location (physical address, restaurant name, virtual link)
  • Event type (meeting, lunch, coffee, party, etc.)
  • Attendees (who else is invited)
  • Special notes (dress code, what to bring, etc.)

Step 2: Parse Relative Dates

Handle conversational dates:

  • "tomorrow" → current date + 1 day
  • "next Monday" → next occurrence of Monday
  • "in two weeks" → current date + 14 days
  • "Dec 5" → December 5 of current year (or next if passed)

Step 3: Check Calendar for Conflicts

BEFORE creating the event:

# Get user's calendar for that date
mcp__pd__google_calendar-list-events(
  instruction="Get all events for [date], between [start_time - bufferMinutes] and [end_time + bufferMinutes]"
)

Look for:

  • Direct conflicts (overlapping times)
  • Buffer violations (< bufferMinutes between events)
  • Lunch conflicts (check workingHours.lunch* from config)
  • End-of-day violations (past workingHours.end)

Step 4: Report Availability

Tell the user:

If free:

You're free at [time] on [date].

If conflict exists:

That conflicts with:
- [event name] from [start] to [end]

Your schedule that day:
9:30am - 10:30am: Team standup
10:30am - 12:00pm: FREE
12:00pm - 1:30pm: Lunch
1:30pm - 3:00pm: [Proposed event would go here]
3:00pm - 4:00pm: Client call

Step 5: Create the Event

If user confirms or no conflict exists:

mcp__pd__google_calendar-create-event(
  instruction="Create event with:
  - Title: [descriptive title with location if includeLocation=true]
  - Date: [YYYY-MM-DD]
  - Start time: [HH:MM] [timezone]
  - End time: [HH:MM] [timezone]
  - Location: [physical address or link]
  - Description: [context about who invited, what it's about]
  - Attendees: [email addresses]
  "
)

Title format examples:

  • If includeLocation: true: "Lunch with Mike at Soho House"
  • If includeLocation: false: "Lunch with Mike"
  • If includeAttendees: true: "Meeting with Mike, Sarah, John"

Timezone: Always use user's timezone from config unless explicitly scheduling with someone in another timezone.

Step 6: Confirm Addition

Provide:

  • Event summary
  • Calendar link for verification
  • Note any adjustments made (e.g., moved 15min earlier to respect buffer)

Handling Tentative Events

For events pending confirmation:

  1. Create with "HOLD:" prefix

    Title: "HOLD: Call with Jean (pending confirmation)"
    
  2. Add note in description

    Description: "(pending confirmation) Call with Jean Labuschagne about consulting opportunity"
    
  3. Update when confirmed

    • Remove "HOLD:" prefix
    • Update description to remove "pending" note
  4. Delete if falls through

    • Remove the calendar event
    • Log in CRM why it didn't happen (if tracking deals)

Timezone Handling

For Same-Timezone Contacts

Use user's timezone from config:

Time: 2:00 PM America/Chicago

For Different-Timezone Contacts

When scheduling with someone in another timezone:

  1. Specify both timezones in email:

    "How about 9am Chicago time (4pm Zurich)?"
    
  2. Double-check conversion:

    • Look up their timezone
    • Calculate offset from user's timezone
    • Verify conversion is correct
    • Account for DST differences
  3. Common international contacts: Keep a mental note of frequent timezone conversions:

    • US East Coast: +1 hour from Chicago (America/New_York)
    • UK: +6 hours from Chicago (Europe/London)
    • Central Europe: +7 hours from Chicago (Europe/Zurich)
    • Tokyo: +15 hours from Chicago (Asia/Tokyo)
  4. Create event in user's timezone:

    Title: "Call with Jean in Zurich"
    Time: 9:00 AM America/Chicago
    Description: "9am Chicago / 4pm Zurich - Call with Jean Labuschagne"
    

Working Hours Awareness

Checking Availability

When someone asks "when are you free?":

  1. Check user's workingHours from config
  2. Look for gaps between existing events
  3. Respect bufferMinutes between meetings
  4. Avoid scheduling during lunch hours
  5. Prefer morning or afternoon blocks

Typical Day Structure

Based on config defaults:

9:30am - Start of working day
    ↓
[Morning block for meetings/work]
    ↓
12:00pm - 1:30pm - Lunch (avoid scheduling)
    ↓
[Afternoon block for meetings/work]
    ↓
4:30pm - End of working day

Buffer Management

Apply bufferMinutes (default: 15) between events:

10:00am - 11:00am: Meeting A
[15 min buffer]
11:15am - 12:00pm: Meeting B

Don't schedule back-to-back unless user explicitly requests.

Recurring Events

For recurring events (weekly standups, monthly check-ins):

mcp__pd__google_calendar-create-event(
  instruction="Create recurring event:
  - Title: [name]
  - Frequency: [daily/weekly/monthly]
  - Day: [Monday, Tuesday, etc. for weekly]
  - Time: [HH:MM]
  - Duration: [minutes]
  - Until: [end date or 'indefinitely']
  "
)

Focus Time / Blocking

For work blocks or focus time:

mcp__pd__google_calendar-create-event(
  instruction="Create focus time block:
  - Title: 'Focus Time' or 'Deep Work'
  - Mark as: Busy
  - Visibility: Private (optional)
  - Duration: [typically 2-4 hours]
  - Recurring: [if regular pattern]
  "
)

Integration with Email Skill

When email-management skill sees scheduling language:

  1. Extract event details
  2. Call this skill to check conflicts
  3. Report back to email skill
  4. Email skill includes availability in draft response
  5. This skill creates event once confirmed

Seamless handoff between skills.

Common Scenarios

Scenario 1: Lunch Invitation

Email: "Want to grab lunch next Tuesday?"

1. Check calendar for next Tuesday
2. Check lunch hours (12:00-1:30pm from config)
3. Look for conflicts in that window
4. Report: "You're free for lunch on Tuesday Dec 5"
5. Create tentative hold
6. Once confirmed, create proper event with restaurant location

Scenario 2: Meeting Request with Multiple Options

Email: "Can we meet Monday or Tuesday afternoon?"

1. Check both Monday and Tuesday afternoons
2. Identify all free slots after lunch
3. Report: "You're free:
   - Monday 2:00pm-4:30pm
   - Tuesday 1:30pm-3:00pm, 4:00pm-4:30pm"
4. Let user choose
5. Create event for chosen slot

Scenario 3: International Call

Email from Switzerland: "9am your time?"

1. Confirm user's timezone (America/Chicago)
2. Calculate Switzerland time (4pm CET)
3. Check 9am Chicago for conflicts
4. Report availability
5. Create event with both timezones in description

Common Mistakes to Avoid

❌ Not Checking Conflicts

Problem: Double-booking user Solution: ALWAYS check calendar before confirming availability

❌ Wrong Timezone

Problem: Event created in wrong timezone, user misses meeting Solution: Use timezone from config, verify conversions carefully

❌ Ignoring Buffers

Problem: Back-to-back meetings with no break Solution: Apply bufferMinutes between events

❌ Scheduling During Lunch

Problem: Booking meetings during lunch hours Solution: Check workingHours.lunchStart/End from config

❌ Vague Event Titles

Problem: "Meeting" with no context Solution: Include who, what, where based on eventNaming preferences

❌ Forgetting to Create Holds

Problem: User verbally commits but event not tracked Solution: Always create HOLD events for tentative commitments

Integration Checklist

Before completing a calendar task:

  • Loaded user's calendar preferences from config
  • Checked for conflicts with sufficient buffer
  • Verified timezone is correct
  • Respected working hours and lunch time
  • Used descriptive event title per preferences
  • Added location if includeLocation enabled
  • Included relevant attendees
  • Added context in description
  • Confirmed event was created successfully
  • Provided calendar link to user

Success Criteria

You're managing calendar well when:

  • No double-bookings occur
  • User has appropriate buffers between meetings
  • Timezone conversions are accurate
  • Event titles are clear and helpful
  • Working hours are respected
  • Conflicts are caught before committing
  • Integration with email is seamless

Remember

Calendar management is about protecting user's time and making scheduling effortless. Be proactive, be accurate, and always check conflicts first.

Office Admin CRM Management

When to Use This Skill

Use this skill ANY time you:

  • Add contacts from emails or conversations
  • Create or update deals
  • Log interactions with people
  • Search for existing contacts or companies
  • Work with relationships between contacts
  • Backfill CRM data from email history
  • Need to check if a contact already exists

User CRM Preferences

Load user preferences from ~/.claude/office-admin-config.json:

{
  "crm": {
    "contactTypes": "professional" | "personal" | "mixed",
    "detailLevel": "minimal" | "standard" | "detailed",
    "autoLogInteractions": true | false,
    "trackRelationships": true | false
  }
}

Adapt your CRM workflow to match these preferences.

Core Principles

1. Always Check Before Adding

NEVER add a contact or company without checking if they already exist first.

# WRONG - adds without checking
mcp__pagen__add_contact(name="John Doe", email="john@example.com")

# RIGHT - check first
mcp__pagen__find_contacts(query="john@example.com")
# Only add if not found

2. Associate Contacts with Companies

When you know someone's company, ALWAYS link them:

# Add company first (if needed)
mcp__pagen__add_company(
  name="Acme Corp",
  domain="acme.com",
  industry="Technology"
)

# Then add contact with company association
mcp__pagen__add_contact(
  name="John Doe",
  email="john@example.com",
  company_name="Acme Corp",
  phone="+1-555-0100"
)

3. Log Meaningful Interactions

After ANY significant email exchange, meeting, or conversation, log it (if user has autoLogInteractions enabled):

mcp__pagen__log_contact_interaction(
  contact_id="abc-123",
  note="Discussed Q4 partnership. They're interested in our AI tool. Follow up after Thanksgiving.",
  interaction_date="2025-11-22"
)

Adjust detail level based on user's detailLevel preference:

  • Minimal: Just key facts
  • Standard: Context about interaction
  • Detailed: Thorough notes with quotes, decisions, next steps

Available CRM Tools

Core Tools

  • mcp__pagen__add_company(name, domain, industry, notes) - Add new company
  • mcp__pagen__add_contact(name, email, company_name, phone, notes) - Add new contact
  • mcp__pagen__update_contact(id, name, email, phone, notes) - Update existing contact
  • mcp__pagen__create_deal(title, company_name, amount, stage, contact_name, initial_note, expected_close_date, currency) - Create business opportunity
  • mcp__pagen__update_deal(id, title, stage, amount, expected_close_date) - Update deal status

Search & Query Tools

  • mcp__pagen__query_crm(entity_type, query, filters, limit) - Universal search (contact/company/deal/relationship)
  • mcp__pagen__find_contacts(query, company_id, limit) - Search contacts by name/email
  • mcp__pagen__find_companies(query, limit) - Search companies by name/domain

Relationship & Interaction Tools

  • mcp__pagen__log_contact_interaction(contact_id, note, interaction_date) - Log interactions
  • mcp__pagen__link_contacts(contact_id_1, contact_id_2, relationship_type, context) - Connect contacts
  • mcp__pagen__find_contact_relationships(contact_id, relationship_type) - View relationships
  • mcp__pagen__add_deal_note(deal_id, content) - Add notes to deals

Deal Stages

Use these standard stages for deals:

  • prospecting - Initial conversations, exploring possibilities
  • qualification - Determining if it's a real opportunity with potential
  • proposal - Active proposal or pitch in progress
  • negotiation - Terms being discussed, getting close
  • closed_won - Deal completed successfully
  • closed_lost - Deal didn't happen (still valuable to track why)

Workflow: Adding Contact from Email

When processing an email with a new person:

# 1. Check if contact exists
mcp__pagen__find_contacts(query="person@example.com")

# 2. If not found, extract info from email:
#    - Full name
#    - Email address
#    - Company (if mentioned)
#    - Phone (if in signature)
#    - Context about them (adapt detail level to user's preference)

# 3. Check if company exists (if applicable)
mcp__pagen__find_companies(query="Example Corp")

# 4. Add company if needed
mcp__pagen__add_company(
  name="Example Corp",
  domain="example.com",
  industry="Technology",
  notes="[Context based on user's detailLevel preference]"
)

# 5. Add contact with company association
mcp__pagen__add_contact(
  name="Jane Smith",
  email="jane@example.com",
  company_name="Example Corp",
  phone="+1-555-0200",
  notes="[Context based on user's detailLevel preference]"
)

# 6. Log the interaction (if autoLogInteractions enabled)
mcp__pagen__log_contact_interaction(
  contact_id="<returned_id>",
  note="[Detail based on user's detailLevel preference]",
  interaction_date="2025-11-22"
)

# 7. Track relationships (if trackRelationships enabled)
# If they mention knowing someone else in your CRM:
mcp__pagen__link_contacts(
  contact_id_1="<jane_id>",
  contact_id_2="<bob_id>",
  relationship_type="colleague",
  context="Jane mentioned working with Bob at previous company"
)

Workflow: Creating a Deal

When you identify a business opportunity:

# 1. Ensure contact and company exist (see above)

# 2. Create the deal
mcp__pagen__create_deal(
  title="AI Consulting Project - Example Corp",
  company_name="Example Corp",
  contact_name="Jane Smith",
  stage="prospecting",
  amount=50000,  # in cents
  currency="USD",
  expected_close_date="2026-03-01",
  initial_note="[Detail based on user's detailLevel preference]"
)

# 3. Log updates as deal progresses
mcp__pagen__add_deal_note(
  deal_id="<deal_id>",
  content="[Detail based on user's detailLevel preference]"
)

# 4. Update deal stage when it changes
mcp__pagen__update_deal(
  id="<deal_id>",
  stage="proposal",
  amount=75000  # updated after scope discussion
)

What Counts as a "Deal"?

Track these as deals:

  • ✅ Consulting or advisory opportunities
  • ✅ Speaking engagements with compensation
  • ✅ Book publishing opportunities
  • ✅ Partnership or collaboration opportunities
  • ✅ Investment opportunities
  • ✅ Real estate transactions
  • ✅ Major purchases or sales
  • ✅ Sponsorships (being a sponsor or receiving sponsorship)

Don't track as deals:

  • ❌ Social lunches with no business angle
  • ❌ Informational coffee chats
  • ❌ Personal favors or introductions
  • ❌ Newsletter subscriptions
  • ❌ Generic networking

Email Backfill Best Practices

When backfilling CRM from email history:

  1. Work in time-bounded batches - Process 1-2 months at a time
  2. Start with SENT emails - You're usually the initiator, so sent emails have better signal
  3. Then do INBOX - Catch incoming opportunities you might have missed
  4. Skip noise - Ignore newsletters, receipts, automated emails
  5. Focus on humans - Only add real people they interact with
  6. Log context - Include what was discussed, not just "sent email"
  7. Check for dupes - Always search before adding
  8. Respect detailLevel - Match note detail to user's preference

Contact Types and Filtering

Based on user's contactTypes setting:

Professional:

  • Focus on work relationships
  • Track company associations carefully
  • Emphasize business context in notes
  • Create deals for opportunities

Personal:

  • Focus on personal relationships
  • Company associations optional
  • Emphasize personal context (how you met, shared interests)
  • Deals less common

Mixed:

  • Handle both types
  • Clearly distinguish in notes which category
  • Be flexible with detail level
  • Track both business and personal context

Common Mistakes to Avoid

❌ Adding without checking

# This creates duplicates!
mcp__pagen__add_contact(name="Bob Jones", email="bob@test.com")
mcp__pagen__add_contact(name="Bob Jones", email="bob@test.com")

❌ Not associating with company

# Missing valuable context
mcp__pagen__add_contact(
  name="Jane Smith",
  email="jane@bigcorp.com"
  # Should include company_name="BigCorp"!
)

❌ Wrong level of detail

# User has detailLevel: "minimal" but you write:
mcp__pagen__log_contact_interaction(
  contact_id="abc",
  note="Had extensive discussion about their company's AI strategy including their plans for Q1 implementation of LLM-based customer support, concerns about hallucinations, budget constraints around $50k, and follow-up scheduled for next Tuesday at 2pm to review proposal draft..."
)

# Should be:
mcp__pagen__log_contact_interaction(
  contact_id="abc",
  note="Discussed AI strategy. Follow up Tue 2pm with proposal."
)

❌ Not tracking deals

# Someone asks about consulting work - this is a deal!
# Don't just log it as an interaction
# Create a deal to track the opportunity

❌ Over-logging when autoLogInteractions is false

# If user disabled auto-logging, only log:
# - Significant milestones
# - Explicit user request
# - Deal-related interactions

Data Quality Guidelines

Good Contact Notes (based on detailLevel)

Minimal:

  • How you met
  • Their role or what they do
  • One-line context

Standard:

  • How you met
  • What they're interested in
  • Current conversation or project
  • Key personal detail (timezone, etc.)

Detailed:

  • Comprehensive background
  • Detailed conversation history
  • Personal preferences and patterns
  • Relationship mapping
  • Next steps and follow-ups

Good Company Notes

Include (scaled to detailLevel):

  • Industry or sector
  • Company size if relevant
  • What they do
  • Context about the relationship

Good Interaction Notes

Include (scaled to detailLevel):

  • What was discussed
  • Outcomes or decisions
  • Next steps or follow-ups
  • Date of interaction

Integration with Email Skill

When email-management skill identifies a new contact:

  1. Automatically trigger CRM workflow
  2. Check for existing contact
  3. Add if new (respecting CRM preferences)
  4. Log interaction if enabled
  5. Return to email workflow

Summary Checklist

Before adding to CRM, ask yourself:

  • ☐ Did I check user's CRM preferences from config?
  • ☐ Did I search to see if this contact already exists?
  • ☐ Did I search to see if their company already exists?
  • ☐ Did I include company association if I know it?
  • ☐ Did I match the user's preferred detail level?
  • ☐ Is autoLogInteractions enabled? Should I log this?
  • ☐ Is this a deal I should be tracking?
  • ☐ Should I track relationships to other contacts?
  • ☐ Did I include phone number if available?

Remember: The CRM is only valuable if the data is clean and contextual. Quality over quantity, always.

Success Criteria

You're managing CRM well when:

  • No duplicate contacts are created
  • Contact notes match user's preferred detail level
  • Interactions are logged appropriately (not too much, not too little)
  • Deals are tracked consistently
  • Relationships are mapped when user has that enabled
  • Integration with email workflow is seamless

Email Management with Office Admin

Use this skill when handling:

  • Checking inbox or finding specific emails
  • Drafting email replies
  • Adding events from emails to calendar
  • Managing email workflows
  • Bulk email triage

Core Principles

  1. Always draft, never send - Save emails as drafts for user review before sending
  2. Threading is critical - Replies must appear in the correct conversation thread
  3. Match user's voice - Reference their office-admin config for tone and style
  4. Extract structured data - Pull event details, action items, contact info from emails
  5. Proactive calendar integration - Auto-check conflicts and add events

User Style Configuration

Before drafting emails, load the user's style from ~/.claude/office-admin-config.json:

{
  "email": {
    "tone": "ultra-terse" | "conversational" | "professional" | "warm",
    "signature": "none" | "minimal" | "full",
    "formality": "casual" | "standard" | "formal",
    "responseLength": "minimal" | "balanced" | "detailed",
    "patterns": ["common phrases they use"],
    "customGuidelines": "Additional freeform style notes"
  }
}

If config doesn't exist, prompt user to run /setup-office-admin first.

Email Drafting Workflow

Step 1: Find the Thread

When drafting a reply, ALWAYS search for the original email first:

Search for: [subject] from [sender name]
Get: Full email content, thread ID, message ID, recipient email

Why: You need context AND threading information. Skipping this = standalone draft instead of threaded reply.

Step 2: Get Threading Details

Extract from search results:

  • thread_id - Links all messages in the conversation
  • message_id - The specific message you're replying to (usually most recent)
  • recipient_email - The To: address (CRITICAL - tool doesn't auto-extract!)

Critical: All three are required for proper threading. Missing any = broken draft.

Step 3: Draft Using User's Voice

Reference their config for:

Tone Guidelines:

  • Ultra-terse: 1-2 lines, no fluff, direct
  • Conversational: Casual but complete, friendly
  • Professional: Formal, structured, proper grammar
  • Warm: Friendly, personal, include pleasantries

Signature Guidelines:

  • None: No sign-off, message ends immediately
  • Minimal: Simple "Best," or "Thanks,"
  • Full: Complete signature block from config

Response Length:

  • Minimal: One-liners when possible
  • Balanced: 2-3 sentences typical
  • Detailed: Thorough explanations

User Patterns: Use their common phrases from config patterns array when appropriate.

Step 4: Create Threaded Draft

When creating the draft, specify:

  • To: Recipient's email address (CRITICAL - always explicit!)
  • Thread ID (to keep it in conversation)
  • In-Reply-To message ID (the message you're replying to)
  • Subject (maintain thread subject, usually "Re: [original]")
  • Body (match user's voice from config)
  • Signature (based on user's preference)

CRITICAL: Always explicitly provide the To: email address. The MCP tool does NOT automatically extract the recipient from the thread - if you omit it, it will create a broken draft with invalid addresses.

Example tool call structure:

To: sender@example.com
Thread ID: 19a5fc252ad4dd3a
In-Reply-To message ID: 19a711957d96874d
Subject: Re: Project Discussion
Body: [message in user's style]
[Signature if configured]

Step 5: Verify Threading

After creating draft, confirm:

  • Draft appears in the correct conversation thread
  • Subject line maintains thread format
  • Draft is saved (not sent)

If threading failed:

  1. Get correct thread ID and message ID again
  2. Recreate draft with proper IDs
  3. Don't create a new standalone email

Step 6: Iterate on Feedback

User will refine wording:

  • Update the draft with changes
  • Maintain proper threading
  • Keep user's voice consistent

Calendar Integration

IMPORTANT: When emails contain event information, PROACTIVELY add them to the calendar and check for conflicts. Don't wait for user to ask.

Step 1: Extract Event Details

Look for:

  • Date and time
  • Location
  • Event title/description
  • Attendees/who's invited
  • Any special notes

Step 2: Check Calendar for Conflicts

BEFORE creating the event:

  1. Check user's calendar for the event date
  2. Look for conflicts around the event time
  3. Note any existing commitments
  4. Reference their working hours from config

Why: User needs to know if there's a conflict before committing.

Step 3: Report Conflicts or Availability

Tell the user:

  • "You're free at [time] on [date]" ✅
  • "That conflicts with [existing event] at [time]" ⚠️
  • Show the relevant portion of the day's schedule

Step 4: Add Event to Calendar (if appropriate)

If user confirms or if there's no conflict, create the event with:

  • Clear title (include location if helpful)
  • Correct date/time with timezone awareness (from config)
  • Location field
  • Description noting who invited/context
  • Attendees (if it's a meeting with others)

Example:

Title: "Lunch with Mike Evans at Soho House"
Date: December 3, 2025
Time: 12:00 PM to 1:30 PM ([User's Timezone from config])
Location: Soho House
Description: "Lunch invitation from Mike Evans to discuss Q1 planning"
Attendees: mike@example.com

Step 5: Confirm Addition

Let user know the event was added and provide:

  • Calendar link for verification
  • Note any conflicts that were identified
  • Confirm if adjustments are needed

Step 6: Handle Tentative Events

For events pending confirmation:

  • Create calendar event with "HOLD:" prefix in title
  • Example: "HOLD: Call with Jean (pending confirmation)"
  • Add "(pending confirmation)" in description
  • Update to remove "HOLD" once confirmed
  • Delete if falls through

Step 7: Timezone Handling

When scheduling with people in other timezones:

  • Use user's timezone from config as primary
  • Specify BOTH timezones in the email
  • Example: "9am [your timezone] (4pm their timezone)"
  • Double-check timezone conversion before sending

Inbox Triage

When checking inbox:

Step 1: Search for Unread

Get recent unread emails with:

  • Sender
  • Subject
  • Date
  • Preview snippet

Step 2: Categorize

Group mentally by type:

  • Urgent/Today: Meetings, time-sensitive requests
  • Action needed: Need response or calendar add
  • FYI: Updates, newsletters
  • Archive: No action needed, informational only

NEVER categorize as "DELETE" - Users should archive instead of deleting.

For spam/unwanted emails:

  • Mark as spam using Gmail's spam function (if truly spam)
  • Unsubscribe from newsletters (if there's an unsubscribe link)
  • Archive everything else (don't delete - email storage is cheap, deletion is permanent)

Step 3: Summarize Clearly

Present in order of priority:

  • Recent/urgent first
  • Group related emails (threads)
  • Highlight action items
  • Note any follow-ups needed

Step 4: Use Subagents for Bulk Processing

For large triage operations (10+ emails):

  • Use Task tool with general-purpose subagent
  • Have subagent categorize all emails
  • Subagent can draft multiple replies in one go
  • More efficient than processing one-by-one

Bulk Email Processing with Subagents

When user asks to triage many emails or handle multiple replies:

  1. Use subagent for triage:

    • Pass clear categorization criteria
    • Have subagent check calendars for scheduling
    • Pass user's email style config to subagent
    • Get comprehensive report back
  2. Use subagent for bulk drafting:

    • Provide list of emails needing replies
    • Give subagent user's voice guidelines from config
    • Subagent creates all drafts with proper threading
    • Review and user sends

Example prompt structure for subagent:

Triage all unread emails in inbox. Categorize as:
- ACTION NEEDED (with specific next steps)
- CALENDAR (extract event details, check conflicts)
- ARCHIVE (no action needed)

For ACTION NEEDED, draft replies using this style:
[Include user's email config]

Return comprehensive report.

Common Mistakes to Avoid

❌ Creating Standalone Drafts Instead of Threaded Replies

Problem: Draft appears as new email, not in conversation thread Solution: Always get thread ID and message ID before creating draft

❌ Not Matching User's Voice

Problem: Email doesn't sound like the user Solution: Reference their office-admin config for tone, formality, patterns

❌ Adding Wrong Signature

Problem: Adding "Best," when user configured "none" Solution: Check config email.signature setting

❌ Sending Instead of Drafting

Problem: User can't review before it goes out Solution: ALWAYS save as draft, let user send

❌ Forgetting to Extract Calendar Events

Problem: User has to manually add events later Solution: Proactively offer to add events when you see them in emails

❌ Missing the To: Field

Problem: Draft created with invalid @example.com address that bounces Solution: ALWAYS explicitly provide recipient email address from thread search

❌ Wrong Timezone

Problem: Event added in wrong timezone Solution: Use timezone from user's config (default: their local timezone)

Integration Checklist

Before completing an email task, verify:

  • Loaded user's office-admin config for style preferences
  • Found original email/thread for context
  • Got thread ID, message ID, AND recipient email if replying
  • Drafted in user's voice (matched config settings)
  • Created as DRAFT (not sent)
  • Verified proper threading if reply
  • Extracted and added calendar events if present
  • Checked for scheduling conflicts
  • Summarized what was done for user

CRM Integration

When processing emails with new contacts:

  • Check if contact exists in CRM
  • Add to CRM if significant contact
  • Log interaction in CRM
  • Associate with company if applicable

See office:crm-management skill for details.

Success Criteria

You've successfully handled email tasks when:

  • Drafts appear in correct conversation threads
  • User says "looks good" without needing changes
  • Calendar events are added proactively
  • Inbox summaries surface what matters
  • Process feels efficient and natural
  • Voice matches user's configured style

Remember

Email is personal communication using the user's voice. The goal is to save time while maintaining authentic, effective communication that sounds like THEM.

When in doubt: Check their config, follow their patterns, and always draft first.

Office Onboarding

Welcome to Office! This skill helps you set up your personal productivity style so that the assistant can help you manage email, calendar, and contacts in a way that matches YOUR preferences.

When to Use This Skill

  • First time installing office-admin
  • Want to update your productivity style preferences
  • Need to configure how email drafts should sound
  • Setting up your working hours and calendar preferences
  • Defining your CRM workflow patterns

Onboarding Process

Step 1: Introduce Yourself

Ask the user:

  1. What should I call you? (Their preferred name/nickname)
  2. What's your timezone? (Default: America/Chicago)
  3. What are your typical working hours? (Default: 9:30am - 4:30pm, lunch 12:00-1:30pm)

Step 2: Email Communication Style

Ask about their email preferences:

  1. Email Tone - How do you typically write emails?

    • Ultra-terse (1-2 lines, no fluff, get to point)
    • Conversational (casual but complete)
    • Professional (formal, structured)
    • Warm (friendly, personal touch)
  2. Email Signatures - Do you use signatures?

    • None (no signatures or sign-offs)
    • Minimal ("Best," or "Thanks,")
    • Full signature block
  3. Formality Level

    • Super casual (lowercase is fine, minimal punctuation)
    • Standard (proper grammar and capitalization)
    • Formal (perfect grammar, structured sentences)
  4. Response Length

    • Minimal (one-liners when possible)
    • Balanced (2-3 sentences typical)
    • Detailed (thorough explanations)
  5. Specific Patterns - Any phrases or patterns you always use?

    • Examples: "Does [time] work for you?", "Let's sync on this", specific greetings

Step 3: Calendar Preferences

Ask about calendar management:

  1. Default meeting duration (Default: 30 minutes)
  2. Buffer time between meetings (Default: 15 minutes)
  3. Calendar link for scheduling (If they have one)
  4. Event naming preferences (Include location? Attendee names?)
  5. Auto-add events from email? (Yes/No - should calendar skill proactively add events)

Step 4: CRM Workflow

Ask about contact management:

  1. What type of contacts do you manage?

    • Professional (colleagues, clients, vendors)
    • Personal (friends, family, social)
    • Mixed (both personal and professional)
  2. How detailed should contact notes be?

    • Minimal (just basics)
    • Standard (basic context about relationship)
    • Detailed (thorough interaction logging)
  3. Relationship tracking

    • Track how you know people (who introduced you)
    • Log all interactions automatically
    • Manual logging only

Step 5: Generate Configuration

After gathering preferences, create a configuration file at: ~/.claude/office-admin-config.json

Format:

{
  "version": "1.0",
  "personal": {
    "name": "User's Name",
    "timezone": "America/Chicago",
    "workingHours": {
      "start": "09:30",
      "end": "16:30",
      "lunchStart": "12:00",
      "lunchEnd": "13:30"
    }
  },
  "email": {
    "tone": "ultra-terse",
    "signature": "none",
    "formality": "casual",
    "responseLength": "minimal",
    "patterns": [
      "how about [time]?",
      "that works perfect"
    ],
    "customGuidelines": "Additional freeform guidelines from user"
  },
  "calendar": {
    "defaultDuration": 30,
    "bufferMinutes": 15,
    "schedulingLink": "https://user.cal.com/schedule",
    "autoAddFromEmail": true,
    "eventNaming": {
      "includeLocation": true,
      "includeAttendees": false
    }
  },
  "crm": {
    "contactTypes": "mixed",
    "detailLevel": "standard",
    "autoLogInteractions": true,
    "trackRelationships": true
  }
}

Step 6: MCP Server Setup Guide

After configuration, provide guidance on required MCP servers:

Required Servers:

  1. Gmail - For email management

    • Installation: Follow Gmail MCP setup docs
    • Scopes needed: read, send, drafts, labels
  2. Google Calendar - For calendar management

    • Installation: Follow Calendar MCP setup docs
    • Scopes needed: read, write events
  3. Pagen CRM (optional) - For contact/company/deal management

    • Installation: Set up Pagen MCP server
    • Requires: Database configuration
  4. Notion (optional) - For advanced note-taking integration

    • Installation: Follow Notion MCP setup docs

Provide installation links and next steps.

Step 7: Create Personal Style Guide

Generate a markdown file at ~/.claude/docs/office-admin-style.md with:

# My Office Admin Style Guide

## About Me
- Name: [User's Name]
- Timezone: [Timezone]
- Working Hours: [Hours]

## Email Style

### Tone
[Description of their tone with 3-4 example phrases]

### Typical Responses
- Scheduling: [Example]
- Quick confirms: [Example]
- Declining: [Example]

### What NOT to Do
- [Anti-patterns based on their preferences]

## Calendar Preferences
[Summary of their calendar settings]

## CRM Workflow
[Summary of their contact management approach]

Completing Onboarding

After setup:

  1. Confirm configuration was saved
  2. Show the user their style guide
  3. Suggest they try /triage-email or /draft-email to test
  4. Remind them they can re-run /setup-office-admin to update preferences

Example Interaction

Assistant: I'm using the office:onboarding skill to help you set up your personal productivity style.

What should I call you?

User: Call me Alex

Commands 3

Draft an email in your personal style with guided assistance. Use the office:email-management skill.

Workflow:

  1. Ask clarifying questions:

    • Who is this email to? (name or email address)
    • Is this a reply to an existing email? (yes/no)
    • What's the main purpose? (scheduling, confirming, declining, requesting, etc.)
  2. If replying to existing email:

    • Search for the original email thread
    • Get thread ID, message ID, and recipient email
    • Read original email for context
  3. If calendar-related (scheduling):

    • Use office:calendar-management skill to check availability
    • Include specific available times in draft
    • Note any conflicts that need to be resolved
  4. Draft the email:

    • Load user's style from ~/.claude/office-admin-config.json
    • Match their tone, formality, and response length preferences
    • Use their common phrases from config
    • Apply signature preference (none/minimal/full)
    • CRITICAL: Always include explicit To: email address
  5. Create the draft:

    • Save as DRAFT (never send)
    • Ensure proper threading if reply
    • Verify subject line is appropriate
    • Provide link to draft for user review
  6. Post-draft actions:

    • If email contains event info, offer to add to calendar
    • If mentioning a new contact, offer to add to CRM
    • Summarize what was created

Example interaction:

User: /draft-email

Claude: I'll help you draft an email. Let me ask a few questions:

1. Who is this email to? (name or email address)
2. Is this a reply to an existing email?
3. What's the main purpose? (scheduling, confirming, declining, requesting, etc.)

User: It's a reply to Sarah about scheduling a call next week

Claude: Let me search for Sarah's email... Found it!

I see Sarah asked about scheduling a call to discuss the Q1 project.

Let me check your calendar for next week...

You're available:
- Monday 2:00pm-4:30pm
- Tuesday 9:30am-12:00pm, 1:30pm-4:30pm
- Wednesday 10:00am-12:00pm

I'll draft a reply in your ultra-terse style:

---
**DRAFT CREATED:**

To: sarah@example.com
Subject: Re: Q1 Project Call

that works perfect. tuesday 2pm?

---

Draft saved to Gmail. Would you like me to:
- Add this to your calendar as a hold?
- Adjust the wording?
- Send it now?

Run the office:onboarding skill to set up your personal productivity style, including email voice, calendar preferences, and CRM workflow patterns.

Perform bulk email triage on your inbox:

  1. Use the office:email-management skill
  2. Search for unread emails in your inbox
  3. Categorize each email as:
    • ACTION NEEDED - Requires response or calendar addition
    • CALENDAR - Contains event information (extract and check conflicts)
    • ARCHIVE - Informational only, no action needed
  4. For ACTION NEEDED emails, draft replies using your personal style from ~/.claude/office-admin-config.json
  5. For CALENDAR emails, proactively add events and check for conflicts using office:calendar-management skill
  6. Present a comprehensive summary organized by priority

If there are more than 10 unread emails, use a Task tool with general-purpose subagent for efficient bulk processing.

Format the output as:

## 📧 Inbox Triage Summary

### 🔴 ACTION NEEDED ([count])
1. **From:** [sender] | **Subject:** [subject]
   **Summary:** [brief summary]
   **Draft:** [link to created draft or "Draft created in Gmail"]

### 📅 CALENDAR ([count])
1. **From:** [sender] | **Subject:** [subject]
   **Event:** [event details]
   **Conflicts:** [none | list conflicts]
   **Status:** [added to calendar | hold created | awaiting confirmation]

### 📋 ARCHIVE ([count])
1. **From:** [sender] | **Subject:** [subject]
   **Summary:** [brief summary]

---
**Total processed:** [count] emails

Sponsors

Details

Marketplace
harperreed/office-admin-claude
Category
Community