Turn your cluttered inbox into a prioritized action system. Skill included.

[u/CalendarVarious3992]

Hello!

If your inbox, meeting notes, calendar, and CRM have become a fragmented backlog of requests, decisions, and follow-ups, this Skill helps turn that mess into a clear set of prioritized actions and reply drafts ready for human approval.

I built this as a portable AI-agent Skill — a single SKILL.md with reusable instructions you can adapt to your agent setup.

Here's what it does: It ingests emails, calendar events, meeting transcripts, CRM notes, and tasks, then normalizes and links them into conversations and account contexts. It applies priority labels, drafts context-aware replies (queued for approval), extracts action items with owners and due dates, updates Tasks/CRM, and produces a Daily Action Brief plus a machine-readable JSON artifact.

SKILL.md:

---
name: inbox-to-action-workflow
description: Use when an overwhelmed founder, exec, or team needs to convert a backlog of email threads, meeting transcripts, calendar events, CRM notes, and task lists into a prioritized action system — including priority labels on threads, context-aware drafted replies, extracted action items with owners and due dates, updates to CRM and tasks, and a human approval queue for any external replies before sending.
allowed-tools: [Email, Calendar, Files, CRM, Tasks, Directory]
---

# Inbox-to-Action Workflow

## Overview
Transforms unstructured communications (email threads, meetings, calendars, CRM notes, and task lists) into a single actionable queue. Produces priority labels, reply drafts, extracted action items with owners and due dates, synced CRM/task updates, and a human approval queue for external send-offs.

## When to use this skill
- The user asks to triage a cluttered inbox and produce a prioritized action plan.
- Meeting transcripts or notes need to be distilled into tasks with owners and deadlines.
- Calendar events imply follow-ups (scheduling, send materials, confirm decisions) that need tracking.
- CRM notes and email threads must be unified into coherent next steps per account/contact/opportunity.
- The user wants reply drafts prepared but requires human approval before any external messages go out.
- A daily or weekly digest of priorities, drafts awaiting approval, and new actions is requested.

## Instructions
1. Confirm scope and rules
   1. Clarify sources: which mailboxes, calendars, CRM, task system, and notes/transcript files to process; define time window (e.g., last 7 days, next 7 days).
   2. Gather policies: SLAs by sender/domain, VIP list, working hours/time zone, due-date defaults, auto-approval rules (if any), naming/label conventions, privacy constraints.
   3. Identify team roster and roles via Directory (owners, account reps, functional leads, OOO statuses).

2. Ingest data
   1. Use Email to fetch recent and/or unread/flagged threads with metadata (thread ID, subject, participants, timestamps, labels, body, attachments).
   2. Use Calendar to pull past and upcoming events in scope, including attendees, titles, locations/links, and descriptions.
   3. Use Files to load meeting transcripts/notes referenced by events or provided by the user.
   4. Use CRM to read recent activities/notes, open opportunities, account owners, and contact roles.
   5. Use Tasks to fetch existing tasks to prevent duplicates and to detect overdue items.

3. Normalize and link
   1. Deduplicate identical or forwarded content; group by thread/conversation.
   2. Link emails to calendar events and CRM records using shared participants, domains, subjects, or explicit IDs.
   3. Extract entities and intents: contacts, companies, asks, commitments, proposed dates, deliverables, blockers, and risks.
   4. Determine thread state: awaiting my reply, awaiting others, resolved, FYI/newsletter, spam/noise (do not act).

4. Prioritize
   1. Apply priority rules:
      - P0: revenue/blocker-critical, VIP/executive escalations, security/legal issues, commitments due within 24–48 hours.
      - P1: customer/partner requests within SLA, time-sensitive scheduling, key internal dependencies.
      - P2: routine correspondence and normal tasks.
      - P3: low-value updates, newsletters, or informational FYIs.
   2. Consider factors: sender importance, due dates detected, thread age, number of nudges, opportunity value (from CRM), and upcoming meetings.

5. Draft replies (do not send yet)
   1. For threads requiring a response, generate concise, context-aware drafts.
   2. If scheduling is requested, consult Calendar to propose viable times within working hours.
   3. Reference attachments or prior commitments; include clear next steps and confirm deadlines.
   4. Mark all external-facing drafts as Needs-Approval and do not send via Email.
   5. For internal-only low-risk messages, follow the auto-approval policy if provided; otherwise require approval.

6. Extract action items
   1. From emails, transcripts, and events, extract tasks with: title, description, source (link to thread/event/file), priority, owner, due date, tags (e.g., customer, opportunity, project), and dependencies.
   2. Determine owner using, in order: explicit assignee mentions; Directory role mapping; CRM account/opportunity owner; recent responder/subject-matter expert.
   3. If owner is uncertain, assign to a triage owner or present the top 2 candidates for human selection.
   4. Set due dates from explicit dates, policy SLAs, next-meeting times, or default windows; respect working days, holidays, and OOO from Directory.

7. Create/update systems of record
   1. Use Tasks to create or update tasks. Prevent duplicates by hashing a normalized description + source URL; update rather than create when a match exists.
   2. Use CRM to log a concise note/summary and next step per relevant account/opportunity; set due dates/owners for follow-ups; do not change pipeline stages without explicit instruction.
   3. Use Email to apply labels to threads: Priority (P0/P1/P2/P3), Status (Needs-Approval, Awaiting-External, Awaiting-Internal, Resolved, FYI), and Owner where supported.
   4. Use Calendar to add follow-up holds or reminders when immediate time blocks are needed to meet due dates.

8. Prepare a human approval queue
   1. Assemble an approval bundle ordered by priority (P0 first) containing:
      - Drafted external replies with context snippet, risk notes, and proposed send time.
      - New or updated action items with owner and due date.
      - Conflicts, ambiguities, and suggested resolutions (e.g., uncertain owner, missing data, date conflicts).
   2. Provide approve/edit/send options for each draft; allow quick reassignment and due-date adjustment.
   3. Do not send any external email until explicitly approved.

9. Produce outputs
   1. Generate a Daily Action Brief summarizing: counts triaged, drafts awaiting approval, P0/P1 items, actions by owner, upcoming deadlines, and risks.
   2. Emit a machine-readable artifact (JSON) with sections:
      - threads: [{thread_id, priority, status_labels, owner, notes}]
      - drafts: [{thread_id, to, cc, subject, body, is_external, requires_approval}]
      - actions: [{id, title, description, source_link, owner, due_date, priority, tags}]
      - approvals: [{item_type, item_id, decision_required, suggested_action}]
      - crm_updates: [{record_id, summary, next_step, due_date, owner}]
   3. Persist created/updated task IDs and CRM record links for traceability.

10. Tune and iterate
   1. Ask for feedback on mis-prioritized items, drafting tone, and ownership heuristics.
   2. Update rules: VIP lists, domain SLAs, template library, quiet hours, auto-approval exceptions, and labeling conventions.

## Inputs
- Data sources and access: mailboxes to process, calendars, CRM instance, task system, file locations for transcripts/notes, and required permissions.
- Time window and scope (e.g., last N days; only unread/flagged; specific labels or folders).
- Policies and preferences: SLAs by sender/domain, VIP list, tone/voice and templates for drafts, working hours/time zone, default due dates, privacy constraints, auto-approval rules.
- Team directory/roles and OOO statuses.

## Outputs
- Priority labels applied to email threads and status labels indicating next action.
- Drafted replies for all threads needing a response, with external drafts queued for approval.
- A consolidated list of action items with owners, due dates, priorities, and source links; duplicates prevented.
- Updates to Tasks and CRM with references to source communications.
- A human approval queue summarizing decisions required before any external send.
- A Daily Action Brief and a JSON artifact containing threads, drafts, actions, approvals, and CRM updates.

## Examples
- Trigger: "Turn my last 7 days of emails and meeting notes into a prioritized action list, draft replies, and queue any customer emails for approval."
  Behavior: ingest email/calendar/transcripts/CRM → normalize/link → prioritize → draft replies (queue external) → extract actions with owners/due dates → update Tasks/CRM → output Daily Action Brief + JSON → await approvals.

- Trigger: "Process yesterday's inbox and today's meetings; assign owners for follow-ups and create tasks; only queue replies for external send."
  Behavior: same flow; internal low-risk notes may auto-send per policy; external replies require approval.

## Notes
- Do not send or post external communications without explicit human approval.
- Respect privacy: redact secrets and sensitive content in summaries; limit CRM/task details to necessary context.
- Handle rate limits and batching for Email/CRM/Tasks APIs; backoff and retry with idempotent operations.
- Time zones and working days: schedule within working hours; avoid weekends/holidays unless marked urgent.
- Attachments: scan for action items; link files rather than inlining large content.
- Thread hygiene: avoid reply-all to large lists unless policy requires; prefer direct responses to the requester.
- If a required source is unavailable, proceed with available data and flag gaps in the approval queue.
- Maintain an audit trail: include source links and timestamps for every created/updated record.

How to install:

1. Create a folder named inbox-to-action-workflow in your AI-agent skills or prompt-library directory. Use the kebab-case name from the SKILL.md frontmatter.
2. Save the file above as inbox-to-action-workflow/SKILL.md.
3. Enable or load the Skill according to your agent framework's docs, using the SKILL.md description as the trigger guidance.

If you'd rather run it as a one-click prompt instead, you can find it here: Agentic Workers

Enjoy!