Scans unread emails and produces prioritized highlights using the Eisenhower urgent/important matrix. Activates for inbox highlights, email summaries, morning email scans, or any request to understand what's important in the inbox right now. Scores by sender importance, keywords, action flags, and recency — surfaces up to 10 highlights grouped by quadrant.
From founder-osnpx claudepluginhub thecloudtips/founder-os --plugin founder-osThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Scan all unread emails and produce a prioritized highlight list for inclusion in the daily briefing. Apply the Eisenhower urgent/important matrix to classify each unread message, score it using sender importance, subject keyword signals, action-required flags, recency weighting, and thread activity. Extract a structured highlight for each high-priority email and return up to 10 highlights grouped by quadrant. Feed the resulting highlight list to the briefing assembly step -- this skill handles classification and extraction only, not final briefing formatting.
Classify every unread email into exactly one quadrant. Use the quadrant assignment to determine whether the email surfaces in the briefing highlights and in what order.
Reserve Q1 for emails that demand same-day action AND carry significant consequences if ignored. Look for:
Always surface Q1 emails in the briefing. Mark every Q1 item with "Action needed: yes" and specify the action.
Assign Q2 to emails with strategic weight but no same-day deadline pressure. Look for:
Surface Q2 emails after all Q1 items. Mark action needed only when an explicit request is present.
Assign Q3 to time-sensitive emails that carry low strategic weight. Look for:
Do not surface Q3 emails in the briefing unless the total Q1 + Q2 count is fewer than 5. When included, place them after all Q2 items.
Assign Q4 to emails with no impact on current priorities. Look for:
Never surface Q4 emails in the briefing highlights. Include them only in the aggregate unread count.
Apply these signals to determine the quadrant assignment. Evaluate each signal independently, then use the combined signal profile to select the best-fit quadrant.
Classify the sender into tiers. Use any available context from CRM data, prior interactions, or the user's contact list.
| Tier | Examples | Weight |
|---|---|---|
| Tier 1: Key clients | Known client contacts, accounts with active deals or projects | High |
| Tier 2: Leadership | Direct manager, C-suite, board members | High |
| Tier 3: Direct reports | Team members who report to the user | Medium |
| Tier 4: External VIPs | Investors, advisors, key partners, high-value prospects | Medium |
| Tier 5: Known internal | Colleagues, cross-functional peers | Low |
| Tier 6: Unknown external | First-time senders, cold outreach | Low |
Tier 1 and Tier 2 senders push the email toward Q1 or Q2 unless the content is clearly low-value (e.g., a VIP forwarding a newsletter with no commentary).
Scan the subject line and first 200 characters of the body for these keyword categories. Perform case-insensitive whole-word matching.
Urgency keywords (push toward Q1 or Q3):
Importance keywords (push toward Q1 or Q2):
Low-priority keywords (push toward Q3 or Q4):
Apply keyword signals as modifiers, not overrides. A "newsletter" subject from a Tier 1 client still warrants review -- classify it as Q2 rather than Q4.
Detect explicit requests directed at the user:
Mark any email with a detected action-required flag as "Action needed: yes" and extract a one-phrase description of the required action.
Apply a recency multiplier to break ties within the same quadrant:
Use recency only for ordering within a quadrant, never to promote an email to a higher quadrant. A 3-day-old Q1 email still ranks above a 1-hour-old Q2 email.
Evaluate thread activity as an engagement signal:
Threads with high activity from Tier 1-2 senders push toward Q1 or Q2. Threads with high activity from Tier 5-6 senders push toward Q3 at most.
For each email that qualifies for the briefing, extract a structured highlight record.
| Field | Description | Format |
|---|---|---|
| Sender | Display name and email address | "Jane Smith (jane@acme.com)" |
| Subject | Full subject line, truncated at 80 characters | Plain text |
| Summary | One-line summary of the email's core content | Max 100 characters, plain text |
| Quadrant | Assigned matrix quadrant | Q1, Q2, or Q3 |
| Action Needed | Whether the user must take action | "Yes: [action phrase]" or "No" |
| Recency | When the email arrived | Relative timestamp ("2h ago", "yesterday") |
| Thread Count | Number of unread messages in the thread | Integer (1 if standalone) |
Generate the one-line summary by:
When multiple unread messages belong to the same thread:
Return the highlight list as a structured block for the briefing assembly agent. Use this format:
## Email Highlights
**Unread total**: [N] emails ([M] threads)
**Highlights**: [count] shown of [total qualifying]
### Q1: Urgent & Important
1. **[Subject]** -- [Sender]
[Summary] | Action: [Yes: action phrase / No] | [Recency] | Thread: [count]
2. ...
### Q2: Important
3. **[Subject]** -- [Sender]
[Summary] | Action: [Yes: action phrase / No] | [Recency] | Thread: [count]
4. ...
### Q3: Time-Sensitive (included because fewer than 5 Q1+Q2 items)
5. ...
Omit the Q3 section header entirely when no Q3 items are included. Omit the Q2 section header when no Q2 items are included.
After the highlights, include a Quick Stats footer:
**Quick Stats**: Q1: [n] | Q2: [n] | Q3: [n] | Q4: [n] | Total unread: [N]
Handle reduced data availability without failing:
Collapse the thread into a single highlight. Use the latest message for all extracted fields except Thread Count, which reflects the total unread count in the thread. Apply the highest applicable quadrant from any message in the thread -- if one message is Q2 but the latest reply is Q1, classify the thread highlight as Q1.
Treat pending calendar invites (those awaiting RSVP) as Q3 minimum. Promote to Q2 if the invite sender is Tier 1-2 or the event is within 24 hours. Extract the event title, date, and time into the summary field instead of the email body text.
Distinguish between success notifications (Q4) and failure/error alerts (Q2 or Q1). A CI/CD failure notification for a production deployment is Q1. A successful nightly backup notification is Q4. Look for keywords: "failed", "error", "down", "alert", "warning", "outage" to detect failures.
Extract highlights using the original language for sender and subject. Generate the summary in English regardless of the source language. Note the detected language in parentheses after the summary if it is not English.
When the body is empty or contains only "See attached" / "Please find attached":
When a thread accumulates 5+ messages within 1 hour from 3+ distinct senders and the content is repetitive (acknowledgments, "+1", "thanks"), collapse to a single Q4 highlight and exclude from the briefing. Note in Quick Stats: "1 reply-all storm excluded ([N] messages)."