outlook-search-via-composio

Stars2

Forks1

UpdatedMay 11, 2026 at 21:35

How to search the user's Outlook mailbox effectively using Composio's OUTLOOK_* tools, including query planning and result ranking

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

Folken2

Folken2/nuvel

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Secretaries and Administrative Assistants, Except Legal, Medical, and ExecutiveOffice and Administrative Support Occupations·SOC 43-6014

SKILL.md

readonly

name	outlook-search-via-composio
description	How to search the user's Outlook mailbox effectively using Composio's OUTLOOK_* tools, including query planning and result ranking
when_to_use	The user asks to find, look up, retrieve, or summarize a past email, attachment, or thread. Anything that isn't the currently-open compose or selected message.

Outlook search via Composio

The agent does not call Microsoft Graph directly. The full mailbox is reachable through Composio's hosted MCP server, which exposes Outlook as a family of tools prefixed OUTLOOK_* (exact names vary by Composio version — discover them in the toolset, don't hardcode).

The three-step search pattern

Every search request follows the same shape:

Plan — call plan_email_search("<user's phrase>"). Returns structured filters: from_addresses, keywords, has_attachments, after_iso, before_iso.
Execute — pick the right Composio Outlook tool:
- Listing/filtering by sender or date window → OUTLOOK_LIST_MESSAGES (or whichever the toolset names it).
- Full-text body+subject search → use the $search parameter where available.
- Pull a specific thread → OUTLOOK_GET_CONVERSATION / OUTLOOK_GET_MESSAGE.
- Drafts only → filter isDraft eq true.
Rank — pass the returned hits (as JSON) to rank_search_hits. Recent + frequent-sender hits float to the top.

When to widen, when to narrow

Zero hits → first widen the date window (drop after_iso), then drop keywords one at a time, then try $search instead of exact filters. Tell the user what you widened.
>20 hits → narrow with stronger filters (specific sender, tighter date window, attachment requirement). Don't dump 20 results on the user — show the top 5 ranked, summarize the rest as "12 more".

Common pitfalls

The user says "last week" on a Monday — that usually means the previous Mon–Sun, not the past 7 days. If results from the literal 7-day window look thin, try the prior calendar week.
Display names ≠ email addresses. If plan_email_search returns from_addresses=[] but the user named someone ("emails from Anna"), search by display name in $search instead of as a from-filter.
Attachments in Outlook are not part of the message body by default. Use the attachment-specific tool to fetch them; the body field will not include their contents.

Output shape

When you reply to the user with results, return:

A one-line summary of what you found (count + what you filtered on)
Up to 5 hits as a compact list: [date] sender — subject (one-line snippet)
If you searched and got nothing, say what you tried and offer a wider variant.

Do not paste full email bodies unless the user asked to read one specifically.

More from this repository

same repository

nuvel

Folken2/nuvel

Use when the user wants to build a Google ADK agent — scaffolding a new agent, adding tools/skills/prompts to one, or asking how to structure an ADK project. Triggers on phrases like "create an ADK agent", "build a Google agent", "scaffold an agent", "make an agent that does X", "I need an ADK skeleton", or any task involving generated-agents/, LlmAgent, SkillToolset, or the ADK framework. Also use whenever the user mentions `nuvel`, the `nuvel` CLI, or asks about agent architecture patterns / callbacks / HITL / streaming / ADK prompt engineering — nuvel ships the canonical knowledge skills for those topics. Lean toward triggering — if the task touches Google ADK at all, this skill is in scope.

2026-07-272

adk-task-delegation

Folken2/nuvel

Delegate work to sub-agents with the ADK 2.0 Task API — `mode='task'`, `mode='single_turn'`, `mode='chat'` on `LlmAgent`, the auto-attached `finish_task` tool, and typed contracts via `input_schema` / `output_schema`. Load this skill when one agent needs to hand a bounded unit of work to another and get a validated result back, or when migrating off SequentialAgent / ParallelAgent / LoopAgent.

2026-07-232

adk-skill-creation

Folken2/nuvel

Creating valid SKILL.md files following the agentskills.io specification — frontmatter, instructions, references directory, progressive disclosure (L1/L2/L3), and SkillToolset wiring in agent.py. Load this skill when generating domain skills for an agent.

2026-05-212

adk-workflow-graphs

Folken2/nuvel

Build graph-based agents with ADK 2.0 `Workflow` — declare nodes and edges, route conditionally, fan-out/fan-in in parallel, run dynamic nodes at runtime, and add human-in-the-loop revision cycles. Load this skill whenever the agent needs anything beyond a strictly linear or trivially parallel pipeline.

2026-05-212

adk-agent-patterns

Folken2/nuvel

Agent architecture patterns for Google ADK 2.0 — when to reach for a single LlmAgent, a Workflow graph (new default for multi-step orchestration), or the shortcut classes SequentialAgent / LoopAgent / ParallelAgent. Load this skill when deciding the agent's top-level shape.

2026-05-212

deck-outlining

Folken2/nuvel

Pattern for turning a brief into a coherent deck outline — intent detection, section ratios, draft headings, expansion

2026-05-112

Outlook search via Composio

The three-step search pattern

Every search request follows the same shape:

Plan — call plan_email_search("<user's phrase>"). Returns structured filters: from_addresses, keywords, has_attachments, after_iso, before_iso.

Execute — pick the right Composio Outlook tool:

Listing/filtering by sender or date window → OUTLOOK_LIST_MESSAGES (or whichever the toolset names it).
Full-text body+subject search → use the $search parameter where available.
Pull a specific thread → OUTLOOK_GET_CONVERSATION / OUTLOOK_GET_MESSAGE.
Drafts only → filter isDraft eq true.

Rank — pass the returned hits (as JSON) to rank_search_hits. Recent + frequent-sender hits float to the top.

When to widen, when to narrow

Zero hits → first widen the date window (drop after_iso), then drop keywords one at a time, then try $search instead of exact filters. Tell the user what you widened.

>20 hits → narrow with stronger filters (specific sender, tighter date window, attachment requirement). Don't dump 20 results on the user — show the top 5 ranked, summarize the rest as "12 more".

Common pitfalls

The user says "last week" on a Monday — that usually means the previous Mon–Sun, not the past 7 days. If results from the literal 7-day window look thin, try the prior calendar week.

Display names ≠ email addresses. If plan_email_search returns from_addresses=[] but the user named someone ("emails from Anna"), search by display name in $search instead of as a from-filter.

Attachments in Outlook are not part of the message body by default. Use the attachment-specific tool to fetch them; the body field will not include their contents.

Output shape

When you reply to the user with results, return:

A one-line summary of what you found (count + what you filtered on)

Up to 5 hits as a compact list: [date] sender — subject (one-line snippet)

If you searched and got nothing, say what you tried and offer a wider variant.

Do not paste full email bodies unless the user asked to read one specifically.