outlook-automation

sickn33/antigravity-awesome-skills · updated Apr 10, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill outlook-automation
0 commentsdiscussion
summary

Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rube MCP.

skill.md

Outlook Automation via Rube MCP

Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rube MCP.

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Outlook connection via RUBE_MANAGE_CONNECTIONS with toolkit outlook
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit outlook
  3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
  4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Search and Filter Emails

When to use: User wants to find specific emails across their mailbox

Tool sequence:

  1. OUTLOOK_SEARCH_MESSAGES - Search with KQL syntax across all folders [Required]
  2. OUTLOOK_GET_MESSAGE - Get full message details [Optional]
  3. OUTLOOK_LIST_OUTLOOK_ATTACHMENTS - List message attachments [Optional]
  4. OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT - Download attachment [Optional]

Key parameters:

  • query: KQL search string (from:, to:, subject:, received:, hasattachment:)
  • from_index: Pagination start (0-based)
  • size: Results per page (max 25)
  • message_id: Message ID (use hitId from search results)

Pitfalls:

  • Only works with Microsoft 365/Enterprise accounts (not @hotmail.com/@outlook.com)
  • Pagination relies on hitsContainers[0].moreResultsAvailable; stop only when false
  • Use hitId from search results as message_id for downstream calls, not resource.id
  • Index latency: very recent emails may not appear immediately
  • Inline images appear as attachments; filter by mimetype for real documents

2. Query Emails in a Folder

When to use: User wants to list emails in a specific folder with OData filters

Tool sequence:

  1. OUTLOOK_LIST_MAIL_FOLDERS - List mail folders to get folder IDs [Prerequisite]
  2. OUTLOOK_QUERY_EMAILS - Query emails with structured filters [Required]

Key parameters:

  • folder: Folder name ('inbox', 'sentitems', 'drafts') or folder ID
  • filter: OData filter (e.g., isRead eq false and importance eq 'high')
  • top: Max results (1-1000)
  • orderby: Sort field and direction
  • select: Array of fields to return

Pitfalls:

  • QUERY_EMAILS searches a SINGLE folder only; use SEARCH_MESSAGES for cross-folder search
  • Custom folders require folder IDs, not display names; use LIST_MAIL_FOLDERS
  • Always check response['@odata.nextLink'] for pagination
  • Cannot filter by recipient or body content; use SEARCH_MESSAGES for that

3. Manage Calendar Events

When to use: User wants to list, search, or inspect calendar events

Tool sequence:

  1. OUTLOOK_LIST_EVENTS - List events with filters [Optional]
  2. OUTLOOK_GET_CALENDAR_VIEW - Get events in a time window [Optional]
  3. OUTLOOK_GET_EVENT - Get specific event details [Optional]
  4. OUTLOOK_LIST_CALENDARS - List available calendars [Optional]
  5. OUTLOOK_GET_SCHEDULE - Get free/busy info [Optional]

Key parameters:

  • filter: OData filter (use start/dateTime, NOT receivedDateTime)
  • start_datetime/end_datetime: ISO 8601 for calendar view
  • timezone: IANA timezone (e.g., 'America/New_York')
  • calendar_id: Optional non-primary calendar ID
  • select: Fields to return

Pitfalls:

  • Use calendar event properties only (start/dateTime, end/dateTime), NOT email properties (receivedDateTime)
  • Calendar view requires start_datetime and end_datetime
  • Recurring events need expand_recurring_events=true to see individual occurrences
  • Decline status is per-attendee via attendees[].status.response

4. Manage Contacts

When to use: User wants to list, create, or organize contacts

Tool sequence:

  1. OUTLOOK_LIST_CONTACTS - List contacts [Optional]
  2. OUTLOOK_CREATE_CONTACT - Create a new contact [Optional]
  3. OUTLOOK_GET_CONTACT_FOLDERS - List contact folders [Optional]
  4. OUTLOOK_CREATE_CONTACT_FOLDER - Create contact folder [Optional]

Key parameters:

  • givenName/surname: Contact name
  • emailAddresses: Array of email objects
  • displayName: Full display name
  • contact_folder_id: Optional folder for contacts

Pitfalls:

  • Contact creation supports many fields but only givenName or surname is needed

5. Manage Mail Folders

When to use: User wants to organize mail folders

Tool sequence:

  1. OUTLOOK_LIST_MAIL_FOLDERS - List top-level folders [Required]
  2. OUTLOOK_LIST_CHILD_MAIL_FOLDERS - List subfolders [Optional]
  3. OUTLOOK_CREATE_MAIL_FOLDER - Create a new folder [Optional]

Key parameters:

  • parent_folder_id: Well-known name or folder ID
  • displayName: New folder name
  • include_hidden_folders: Show hidden folders

Pitfalls:

  • Well-known folder names: 'inbox', 'sentitems', 'drafts', 'deleteditems', 'junkemail', 'archive'
  • Custom folder operations require the folder ID, not display name

Common Patterns

KQL Search Syntax

Property filters:

  • from:[email protected] - From sender
  • to:[email protected] - To recipient
  • subject:invoice - Subject contains
  • received>=2025-01-01 - Date filter
  • hasattachment:yes - Has attachments

Combinators:

  • AND - Both conditions
  • OR - Either condition
  • Parentheses for grouping

OData Filter Syntax

Email filters:

  • isRead eq false - Unread emails
  • importance eq 'high' - High importance
  • hasAttachments eq true - Has attachments
  • receivedDateTime ge 2025-01-01T00:00:00Z - Date filter

Calendar filters:

  • start/dateTime ge '2025-01-01T00:00:00Z' - Events after date
  • contains(subject, 'Meeting') - Subject contains text

Known Pitfalls

Account Types:

  • SEARCH_MESSAGES requires Microsoft 365/Enterprise accounts
  • Personal accounts (@hotmail.com, @outlook.com) have limited API access

Field Confusion:

  • Email properties (receivedDateTime) differ from calendar properties (start/dateTime)
  • Do NOT use email fields in calendar queries or vice versa

Quick Reference

Task Tool Slug Key Params
Search emails OUTLOOK_SEARCH_MESSAGES query, from_index, size
Query folder OUTLOOK_QUERY_EMAILS folder, filter, top
Get message OUTLOOK_GET_MESSAGE message_id
List attachments OUTLOOK_LIST_OUTLOOK_ATTACHMENTS message_id
Download attachment OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT message_id, attachment_id
List folders OUTLOOK_LIST_MAIL_FOLDERS (none)
Child folders OUTLOOK_LIST_CHILD_MAIL_FOLDERS parent_folder_id
List events OUTLOOK_LIST_EVENTS filter, timezone
Calendar view OUTLOOK_GET_CALENDAR_VIEW start_datetime, end_datetime
Get event OUTLOOK_GET_EVENT event_id
List calendars OUTLOOK_LIST_CALENDARS (none)
Free/busy OUTLOOK_GET_SCHEDULE schedules, times
List contacts OUTLOOK_LIST_CONTACTS top, filter
Create contact OUTLOOK_CREATE_CONTACT givenName, emailAddresses
Contact folders OUTLOOK_GET_CONTACT_FOLDERS (none)

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

how to use outlook-automation

How to use outlook-automation on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add outlook-automation
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill outlook-automation

The skills CLI fetches outlook-automation from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/outlook-automation

Reload or restart Cursor to activate outlook-automation. Access the skill through slash commands (e.g., /outlook-automation) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.626 reviews
  • Hassan Mensah· Dec 28, 2024

    outlook-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Shikha Mishra· Dec 20, 2024

    outlook-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ganesh Mohane· Dec 16, 2024

    Registry listing for outlook-automation matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noah Shah· Nov 27, 2024

    outlook-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Kabir Patel· Nov 19, 2024

    Registry listing for outlook-automation matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Anika Gupta· Nov 11, 2024

    outlook-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakshi Patil· Nov 7, 2024

    outlook-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chaitanya Patil· Oct 26, 2024

    I recommend outlook-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Benjamin Patel· Oct 18, 2024

    Useful defaults in outlook-automation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • William Smith· Oct 10, 2024

    outlook-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 26

1 / 3