communication-tracker

Communication Tracker Skill

When to use this Skill

Activate when the user:

• Mentions importing or tracking emails, messages, or communications
• Uses keywords: "email", "message", "communication", "screenshot", "chat log", "track", "import"
• Provides image files (screenshots of emails/chats)
• Wants to record external communication updates
• Mentions "import communication", "track message", "record email"
• References specific communication sources (Slack, Teams, Gmail, etc.)
• Asks to add timeline entries from external sources
• Pastes email content or chat logs

Tools Available

This Skill uses the following tools for content extraction:

• mu: Email indexer for reading email content from local maildir
• Claude Vision: Direct image reading for screenshots
• markitdown: Convert various file formats to markdown (PDF, DOCX, XLSX, etc.)

Workflow

Phase 0: First-Time Configuration (One-Time Setup)

Objective: Configure communication tracking preferences on first use.

Trigger: This phase activates only if communications/config.yaml does not exist.

Steps:

1. Detect first-time use:

   ls communications/config.yaml
   

   If file doesn't exist → Proceed with configuration Q&A.

2. Ask configuration questions using AskUserQuestion tool:

   Question 1: Timeline Tracking:

   Timeline Configuration
   
   Should I create a dedicated timeline tracking file?
   This helps maintain chronological order of all communications.
   
   Options:
   1. Yes, create timeline.yaml (structured, machine-readable)
   2. Yes, create timeline.md (human-readable markdown)
   3. Yes, create both formats (Recommended)
   4. No, embed timeline in individual files only
   

   Question 2: Original Data Backup:

   Original Data Backup
   
   Should I backup original source data?
   This preserves unprocessed content for reference.
   
   Options:
   1. Yes, always backup originals in raw/ subdirectory (Recommended)
   2. Yes, only for images/attachments
   3. No, extract content only (no backup)