Process Email Bookmarks Skill
You process bookmarks sent via email (Gmail label "📑 Bookmarks") and integrate them into the Second Brain.
Gmail: See ../_GMAIL.md | Obsidian CLI: See ../_OBSIDIAN.md | Integration: See ../_SECOND_BRAIN.md
Label: 📑 Bookmarks (ID: Label_2765838113845362546)
Processing Workflow
Step 1: Find Unread Bookmark Emails
bash
gog gmail search "label:📑 Bookmarks is:unread" --account=maroffo@gmail.com --json
Step 2: For Each Email Thread
- •Get full thread content:
bash
gog gmail thread get <threadId> --account=maroffo@gmail.com --json
- •
Extract bookmark info:
- •URL (from email body or links)
- •Title (from subject or link text)
- •Description (from email body)
- •Any notes added by user
- •
Categorize per
../_SECOND_BRAIN.mdrouting table - •
Decide: Actionable -> Fetch via WebFetch, extract, add to Second Brain | Reference -> Bookmarks
- •
Integrate via Obsidian CLI:
bash
# Actionable content -> Second Brain obsidian append file="Second Brain - <Topic>" content="<extracted>" # Reference only -> Bookmarks obsidian create path="Bookmarks/<title>.md" content="- [Title](url) - Brief description" silent
- •Update Timeline:
bash
obsidian append file="Second Brain - Timeline" content="- **YYYY-MM-DD** | [Topic] | Source: Email bookmark | -> Second Brain - <File>.md"
- •Mark email as read (see
../_GMAIL.mdfor command)
Output Format
After processing each bookmark:
code
✓ Processed: [Title] → Source: Email (thread: <threadId>) → Added to: Second Brain - [File].md#[Section] → Type: [Actionable/Reference] → Email marked as read
Example
Input email: Subject "Interesting Go library for CLI" with link to charm.sh
Processing:
- •Search unread bookmarks
- •Get thread content
- •Extract URL: https://charm.sh
- •Fetch page content
- •Categorize: Development (Go, CLI)
- •Extract: Charm - Go libraries for CLI apps (Bubble Tea, Lip Gloss, etc.)
- •Add to Second Brain - Development.md
- •Log to Timeline
- •Mark email read
Rules
See ../_SECOND_BRAIN.md for shared rules. Additional:
- •Always fetch full content - don't rely on email snippet alone
- •Mark as read - only after successful integration