Tencent SkillHub · Productivity

Outlook Delegate

Read, search, and manage Outlook emails and calendar via Microsoft Graph API with delegate support. Supports sending as self, as owner (Send As), and on behalf of owner (Send on Behalf). Modified for delegate access from https://clawhub.ai/jotamed/outlook

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md, _meta.json, scripts/outlook-calendar.sh, scripts/outlook-mail.sh, scripts/outlook-token.sh, references/setup.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.1.1

Provenance

Publisher: 87Marc
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 24 sections Open source page

Outlook Delegate Skill

Access another user's Outlook/Microsoft 365 email and calendar as a delegate via Microsoft Graph API. Supports three sending modes: as yourself, as the owner, or on behalf of the owner.

Delegate Architecture

This skill is designed for scenarios where: Your AI assistant (the delegate) has its own Microsoft 365 account The owner has granted the assistant delegate access to their mailbox/calendar The assistant can send emails as itself, as the owner, or on behalf of the owner

Sending Modes Explained

All three modes use the same Graph API call (/users/{delegate}/sendMail with the from field set). The difference between Send As and Send on Behalf is determined entirely by which Exchange permission is granted, not by the API endpoint. ModeCommandExchange Permission Requiredfrom fieldsender fieldWhat Recipient SeesAs Selfsend(none extra)DelegateDelegate"From: Assistant"As Owner (Send As)send-asSendAs onlyOwnerOwner"From: Owner"On Behalf Ofsend-behalfSendOnBehalf onlyOwnerDelegate"From: Assistant on behalf of Owner" ⚠️ CRITICAL: Do NOT grant both SendAs and SendOnBehalf permissions. If both are granted, Exchange always uses SendAs, and the "on behalf of" indication will never appear. Choose ONE based on your desired behavior.

How It Works Under the Hood

When you call send-as or send-behalf, the skill makes the same API call: it sends via the delegate's endpoint with the owner in the from field. Microsoft Graph automatically sets the sender property to the authenticated user (the delegate). Whether the recipient sees "on behalf of" depends solely on the Exchange permission: SendAs permission → Graph sets both sender and from to the owner. No indication of delegation. SendOnBehalf permission → Graph keeps sender as the delegate and from as the owner. Recipient sees "on behalf of."

Config File: ~/.outlook-mcp/config.json

{ "client_id": "your-app-client-id", "client_secret": "your-app-client-secret", "tenant_id": "your-tenant-id", "owner_email": "owner@yourdomain.com", "owner_name": "Owner Display Name", "delegate_email": "assistant@yourdomain.com", "delegate_name": "AI Assistant", "timezone": "America/New_York" } FieldDescriptionclient_idMicrosoft Entra ID App Registration client IDclient_secretMicrosoft Entra ID App Registration client secrettenant_idYour Microsoft Entra tenant ID (auto-detected during setup)owner_emailThe mailbox the assistant accesses as delegateowner_nameDisplay name for the owner (used in From field)delegate_emailThe assistant's own email addressdelegate_nameDisplay name for the assistanttimezoneIANA timezone for calendar operations (e.g., America/New_York, Europe/London, UTC)

1. Microsoft Entra ID App Registration

Create an app registration in Azure Portal: Go to portal.azure.com → Microsoft Entra ID → App registrations New registration: Name: "AI Assistant Mail Access" Supported account types: "Accounts in this organizational directory only" (single tenant) Redirect URI: http://localhost:8400/callback Note the Application (client) ID and Directory (tenant) ID

2. Configure API Permissions

In your app → API permissions → Add a permission → Microsoft Graph → Delegated permissions: Required for all modes: Mail.ReadWrite — Read/write assistant's own mail Mail.Send — Send mail as assistant Calendars.ReadWrite — Read/write calendars User.Read — Read own profile offline_access — Refresh tokens Required for delegate access: Mail.ReadWrite.Shared — Read/write shared mailboxes Mail.Send.Shared — Send on behalf of others Calendars.ReadWrite.Shared — Read/write shared calendars Click "Grant admin consent" (requires admin).

3. Create Client Secret

Certificates & secrets → New client secret Description: "AI Assistant" Expiration: Choose appropriate duration Copy the Value immediately (shown only once)

4. Grant Exchange Delegate Permissions

The owner (or an admin) must grant the assistant access via PowerShell. Choose your sending mode FIRST, then grant the appropriate permissions: # Connect to Exchange Online Install-Module -Name ExchangeOnlineManagement Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com # REQUIRED: Full Mailbox Access (for reading owner's mail) Add-MailboxPermission -Identity "owner@yourdomain.com" ` -User "assistant@yourdomain.com" ` -AccessRights FullAccess ` -InheritanceType All ` -AutoMapping $false # REQUIRED: Calendar Delegate Access Add-MailboxFolderPermission -Identity "owner@yourdomain.com:\Calendar" ` -User "assistant@yourdomain.com" ` -AccessRights Editor ` -SharingPermissionFlags Delegate Then choose ONE of the following — do NOT grant both: # OPTION A: Send As (emails appear directly from owner, no indication) Add-RecipientPermission -Identity "owner@yourdomain.com" ` -Trustee "assistant@yourdomain.com" ` -AccessRights SendAs ` -Confirm:$false # OPTION B: Send on Behalf (emails show "assistant on behalf of owner") Set-Mailbox -Identity "owner@yourdomain.com" ` -GrantSendOnBehalfTo "assistant@yourdomain.com" Verify permissions: # Check mailbox permissions Get-MailboxPermission -Identity "owner@yourdomain.com" | Where-Object {$_.User -like "*assistant*"} # Check Send As Get-RecipientPermission -Identity "owner@yourdomain.com" | Where-Object {$_.Trustee -like "*assistant*"} # Check Send on Behalf Get-Mailbox "owner@yourdomain.com" | Select-Object GrantSendOnBehalfTo # Check Calendar permissions Get-MailboxFolderPermission -Identity "owner@yourdomain.com:\Calendar"

5. Permissions Summary

ActionGraph PermissionExchange PermissionRead owner's mailMail.ReadWrite.SharedFullAccessSend as selfMail.Send(none needed)Send as ownerMail.Send.SharedSendAs onlySend on behalf of ownerMail.Send.SharedSendOnBehalf onlyRead/write owner's calendarCalendars.ReadWrite.SharedEditor

Token Management

./scripts/outlook-token.sh refresh # Refresh expired token ./scripts/outlook-token.sh test # Test connection to both accounts ./scripts/outlook-token.sh get # Print access token ./scripts/outlook-token.sh info # Show configuration info

Reading Owner's Emails

./scripts/outlook-mail.sh inbox [count] # Owner's inbox ./scripts/outlook-mail.sh unread [count] # Owner's unread ./scripts/outlook-mail.sh search "query" [count] # Search owner's mail ./scripts/outlook-mail.sh from <email> [count] # Owner's mail from sender ./scripts/outlook-mail.sh read <id> # Read email content ./scripts/outlook-mail.sh attachments <id> # List attachments

Managing Owner's Emails

./scripts/outlook-mail.sh mark-read <id> # Mark as read ./scripts/outlook-mail.sh mark-unread <id> # Mark as unread ./scripts/outlook-mail.sh flag <id> # Flag as important ./scripts/outlook-mail.sh unflag <id> # Remove flag ./scripts/outlook-mail.sh delete <id> # Move to trash ./scripts/outlook-mail.sh archive <id> # Move to archive ./scripts/outlook-mail.sh move <id> <folder> # Move to folder

Sending Emails

As Assistant (self): ./scripts/outlook-mail.sh send <to> <subject> <body> ./scripts/outlook-mail.sh reply <id> "body" ./scripts/outlook-mail.sh forward <id> <to> [message] Recipient sees: "From: AI Assistant assistant@domain.com" As Owner (Send As — requires SendAs permission, no indication): ./scripts/outlook-mail.sh send-as <to> <subject> <body> ./scripts/outlook-mail.sh reply-as <id> "body" ./scripts/outlook-mail.sh forward-as <id> <to> [message] Recipient sees: "From: Owner owner@domain.com" On Behalf of Owner (requires SendOnBehalf permission): ./scripts/outlook-mail.sh send-behalf <to> <subject> <body> ./scripts/outlook-mail.sh reply-behalf <id> "body" ./scripts/outlook-mail.sh forward-behalf <id> <to> [message] Recipient sees: "From: AI Assistant on behalf of Owner owner@domain.com"

Drafts

./scripts/outlook-mail.sh draft <to> <subject> <body> # Create draft in owner's mailbox ./scripts/outlook-mail.sh drafts [count] # List owner's drafts ./scripts/outlook-mail.sh send-draft <id> # Send draft as self ./scripts/outlook-mail.sh send-draft-as <id> # Send draft as owner ./scripts/outlook-mail.sh send-draft-behalf <id> # Send draft on behalf of owner

Folders & Stats

./scripts/outlook-mail.sh folders # List mail folders ./scripts/outlook-mail.sh stats # Inbox statistics ./scripts/outlook-mail.sh whoami # Show delegate info

Calendar

Viewing Events: ./scripts/outlook-calendar.sh events [count] # Owner's upcoming events (future only) ./scripts/outlook-calendar.sh today # Today's events (timezone-aware) ./scripts/outlook-calendar.sh week # This week's events ./scripts/outlook-calendar.sh read <id> # Event details ./scripts/outlook-calendar.sh calendars # List all calendars ./scripts/outlook-calendar.sh free <start> <end> # Check availability Creating Events: ./scripts/outlook-calendar.sh create <subject> <start> <end> [location] ./scripts/outlook-calendar.sh quick <subject> [time] Date format: YYYY-MM-DDTHH:MM (e.g., 2026-01-26T10:00) Managing Events: ./scripts/outlook-calendar.sh update <id> <field> <value> ./scripts/outlook-calendar.sh delete <id> Fields: subject, location, start, end

Sent Items Behavior

Where the sent copy is saved depends on the endpoint used, not the sending mode: CommandEndpoint UsedSaved Tosend (as self)/users/{delegate}/sendMailDelegate's Sent Itemssend-as/users/{delegate}/sendMailDelegate's Sent Items *send-behalf/users/{delegate}/sendMailDelegate's Sent Items *All draft sends/users/{owner}/messages/{id}/sendOwner's Sent Items * Administrators can configure Exchange to also save a copy in the owner's Sent Items using: Set-Mailbox -Identity "owner@yourdomain.com" -MessageCopyForSentAsEnabled $true -MessageCopyForSendOnBehalfEnabled $true

Troubleshooting

"Access denied" or "403 Forbidden" → Check that the assistant has MailboxPermission on the owner's mailbox "ErrorSendAsDenied" → Missing SendAs or SendOnBehalf permission. Run the PowerShell commands above. Emails don't show "on behalf of" → You may have both SendAs and SendOnBehalf granted. When both exist, Exchange always uses SendAs (which hides the delegate). Remove the SendAs permission if you want "on behalf of" to appear. "The mailbox is not found" → Verify owner_email in config.json is correct "AADSTS90002: Tenant not found" → Check tenant_id in config.json matches your Microsoft Entra tenant "Token expired" → Run outlook-token.sh refresh Wrong timezone for calendar → Update timezone in config.json (use IANA format like America/New_York)

Security Considerations

Credential Protection: The ~/.outlook-mcp/ directory is automatically set to 700 and credential files to 600 No Process Leaks: Token refresh and exchange operations pass secrets via stdin, not command-line arguments Input Sanitization: All user input is JSON-escaped via jq to prevent injection Audit Trail: All actions are logged in the owner's mailbox audit log Scope Limitation: The assistant only has access to what's explicitly granted Revocation: Owner can revoke access via Exchange PowerShell or Outlook settings

Revoking Access

# Remove all permissions Remove-MailboxPermission -Identity "owner@yourdomain.com" -User "assistant@yourdomain.com" -AccessRights FullAccess -Confirm:$false # Remove Send As (if granted) Remove-RecipientPermission -Identity "owner@yourdomain.com" -Trustee "assistant@yourdomain.com" -AccessRights SendAs -Confirm:$false # Remove Send on Behalf (if granted) Set-Mailbox -Identity "owner@yourdomain.com" -GrantSendOnBehalfTo @{Remove="assistant@yourdomain.com"} # Remove Calendar access Remove-MailboxFolderPermission -Identity "owner@yourdomain.com:\Calendar" -User "assistant@yourdomain.com" -Confirm:$false

Files

~/.outlook-mcp/config.json — Configuration (client ID, tenant ID, emails, timezone) ~/.outlook-mcp/credentials.json — OAuth tokens (access + refresh)

v1.1.0

FIXED: Reply command no longer sends duplicate emails (removed dead code that sent a garbage email) FIXED: All reply/forward variants now use proper Graph API threading (createReply/createForward → patch from → send) FIXED: send-as and send-behalf now correctly documented — behavior depends on Exchange permissions, not API endpoint FIXED: send-draft-behalf no longer deletes draft before sending (prevents data loss on send failure) FIXED: All user input is now JSON-escaped via jq to prevent injection and malformed payloads FIXED: Credentials file permissions enforced on every write (chmod 600) FIXED: Config directory permissions enforced (chmod 700) FIXED: Client secrets no longer visible in process list (sent via stdin) FIXED: Calendar events command now shows only future events FIXED: Sent Items behavior documented accurately FIXED: Version number corrected Updated Microsoft Entra ID naming (formerly Azure Active Directory) Setup guide now explicitly warns against granting both SendAs and SendOnBehalf Revocation commands updated (GrantSendOnBehalfTo uses @{Remove=...} syntax)

v1.0.0

Three sending modes: as self, as owner (Send As), on behalf of owner Tenant-specific authentication (no /common endpoint) Configurable timezone for calendar operations Display names for owner and delegate Drafts saved to owner's mailbox Comprehensive PowerShell setup commands Based on outlook v1.3.0 by jotamed (https://clawhub.ai/jotamed/outlook)

Category context

Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

3 Scripts2 Docs1 Config

SKILL.md Primary doc
references/setup.md Docs
scripts/outlook-calendar.sh Scripts
scripts/outlook-mail.sh Scripts
scripts/outlook-token.sh Scripts
_meta.json Config