Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Automate Microsoft 365 mailbox tasks via Microsoft Graph: read, search, draft, send emails for Business and Consumer accounts with device code authentication.
Automate Microsoft 365 mailbox tasks via Microsoft Graph: read, search, draft, send emails for Business and Consumer accounts with device code authentication.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
Requires Node.js (scripts are Node ESM). This skill declares its npm dependency in package.json. After installing/updating the skill, install deps: cd skills/m365-mailbox npm install
Never commit or share token caches. Default secret location (per machine): ~/.openclaw/secrets/m365-mailbox/
During setup, the user chooses: What Graph permissions to request (minimal vs broad) What OpenClaw is allowed to do autonomously vs what must ask for confirmation Two modes: Minimal-consent mode (more secure): request only the scopes required for the chosen feature set. Broad-consent mode (more flexible): request a superset of scopes, but enforce an autonomy policy locally.
Home/Consumer = hotmail.com, outlook.com, live.com Business = Work/School account (Exchange Online)
No third-party API key required. Auth is done via your own Microsoft login (device code flow). Tokens are stored locally per profile on the OpenClaw machine.
node skills/m365-mailbox/scripts/setup.mjs --profile home --tenant consumers --email you@outlook.com --clientId <YOUR_APP_CLIENT_ID> --tz Europe/Vienna node skills/m365-mailbox/scripts/setup.mjs --profile business --tenant organizations --email you@company.com --clientId <IT_PROVIDED_CLIENT_ID> --tz Europe/Vienna
node skills/m365-mailbox/scripts/list-unread.mjs --profile home --top 20 node skills/m365-mailbox/scripts/search.mjs --profile home --query "invoice" --top 20 node skills/m365-mailbox/scripts/get-message.mjs --profile home --id <MSG_ID> node skills/m365-mailbox/scripts/create-draft.mjs --profile home --to you@example.com --subject "Hi" --body "..." node skills/m365-mailbox/scripts/send-draft.mjs --profile home --id <DRAFT_ID>
Many tenants block: creating app registrations as a normal user user consent to new apps Mail.Send or Mail.ReadWrite without admin consent In that case this skill can still work for Business accounts, but only if your IT/SysAdmin provides a clientId for an app registration configured with: Delegated Microsoft Graph permissions (depending on your chosen feature set): Mail.Read, Mail.ReadWrite, Mail.Send, (optional) offline_access Public client flows enabled (Device Code) (Often required) Admin consent granted If you donβt get such a clientId/consent from IT, you can still use the skill with a Consumer account.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.