Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aktsmm avatar

Microsoft Graph Gateway

  • 6 installs
  • 23 repo stars
  • Updated August 4, 2026
  • aktsmm/agent-skills

microsoft-graph-gateway is a Claude skill that routes Microsoft Graph work in a workspace, using workIQ for common reads and Microsoft Graph for writes and precise reads.

About

Routes Microsoft Graph work in a workspace, preferring workIQ for common reads and Microsoft Graph for writes and precise gap-reads. A developer uses it to read or write Outlook mail, calendar, contacts, OneDrive/SharePoint files, Teams, Planner, To Do, users, groups and directory data from VS Code. It classifies each request as read, gap-read or write, enforces explicit confirmation before writes, and executes through a Graph CLI, MCP server or other gateway substrate.

  • Routes M365 requests: workIQ for common reads, Microsoft Graph for writes and precise reads
  • Requires explicit confirmation before any Graph write; deletes disabled by default
  • Executes through a pluggable substrate (Graph CLI, MCP server, or gateway)

Microsoft Graph Gateway by the numbers

  • 6 all-time installs (skills.sh)
  • Ranked #1,691 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

microsoft-graph-gateway capabilities & compatibility

Free skill; requires Microsoft 365 tenant access and a Graph substrate/app registration

Capabilities
biz ops setup · email automation · calendar management
Works with
outlook · sharepoint · teams · gmail · google drive
Use cases
email · api development · orchestration
IDEs
vscode
Pricing
Bring your own API key
From the docs

What microsoft-graph-gateway says it does

Route Microsoft Graph work in this workspace.
SKILL.md
Use Microsoft Graph for all writes.
SKILL.md
npx skills add https://github.com/aktsmm/agent-skills --skill microsoft-graph-gateway

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs6
repo stars23
Last updatedAugust 4, 2026
Repositoryaktsmm/agent-skills

What it does

Read or write Microsoft 365 data (mail, calendar, files, Teams) from VS Code via workIQ or Microsoft Graph.

Who is it for?

Routing and safely executing Microsoft 365 reads and writes across mail, calendar, files, Teams and directory

Skip if: Non-Graph tasks, or when a purely common read is fully answered by workIQ alone

When should I use this skill?

Reading or writing M365 data from VS Code, or needing an exact Graph endpoint, permission or payload

What you get

Correctly routed Graph operations with least-privilege scopes and confirmed writes

  • Routed Graph reads/writes
  • Write confirmation summaries
  • Least-privilege permission profiles

By the numbers

  • 8-step procedure
  • 3 request classes (common read, gap-read, write)

Files

SKILL.mdMarkdownGitHub ↗

Microsoft Graph Gateway

Use this skill as the orchestration shell for Microsoft Graph work in this workspace.

This skill does not try to abstract all of Microsoft Graph into a fixed checklist. Instead, it does two things:

1. Route common read requests to the right source. 2. Enforce safe execution rules before Graph writes or advanced reads.

When To Use

  • The user wants to read or write Microsoft 365 data from VS Code.
  • The request mentions mail, email, inbox, Outlook, meetings, calendar, contacts, OneDrive, SharePoint, Teams, Planner, To Do, users, groups, or Microsoft Graph.
  • The user wants an exact Microsoft Graph endpoint, permission, query option, or payload.
  • WorkIQ can likely answer a common read request, but Graph may be needed as a fallback.

Routing Rules

Read Routing

  • Prefer WorkIQ first for common read scenarios such as inbox checks, meeting lookups, file discovery, and lightweight summaries.
  • Use Microsoft Graph for gap-read scenarios when WorkIQ cannot answer, returns insufficient detail, or the user asks for exact Graph semantics.
  • Go straight to Microsoft Graph when the user asks for:
  • exact endpoint names or raw REST calls
  • precise properties, $select, $filter, $expand, or API version control
  • Teams, Planner, To Do, directory, or permission-oriented data
  • schema, permission, throttling, batching, delta, or webhook behavior

Write Routing

  • Use Microsoft Graph for all writes.
  • Treat send, create, update, move, upload, reply, assign, and respond operations as writes.
  • Require explicit confirmation before any write.
  • Keep delete actions disabled by default or behind a stronger confirmation step.

Operating Model

  • This skill is a thin shell.
  • The execution substrate can be a Graph CLI, a self-hosted MCP server, or another Graph gateway.
  • Do not invent endpoints or permissions from memory when an authoritative lookup is available.
  • Keep delegated and application permission flows separate.
  • Prefer least-privileged scopes and minimal projections.

Procedure

1. Classify the request as common read, gap-read, or write. 2. For common read, try the WorkIQ route first. 3. For gap-read or write, identify the target Microsoft Graph surface. 4. Check the capability, routing, and substrate references before choosing the execution path.

  • raw execution contract
  • permission profiles
  • curated tool catalog

5. For Microsoft Graph execution, determine:

  • resource area
  • endpoint or tool
  • API version
  • least-privileged permission profile
  • minimal response shape

6. Before any write, present a concise confirmation summary covering target, action, and payload intent. 7. Execute through the chosen substrate. 8. Report the result, including any permission, throttling, or follow-up concerns.

Script Entry Points

  • Use Invoke-GraphGateway.ps1 for raw Graph execution through the selected substrate.
  • Use invoke-graph-gateway.sh on macOS or Linux when pwsh is installed.
  • Use New-GraphWriteConfirmation.ps1 to generate a concise write confirmation summary before execution.
  • Use Test-GraphGatewayScaffold.ps1 to smoke-test the current scaffold without live Graph execution.
  • Use test-graph-gateway-scaffold.sh on macOS or Linux when pwsh is installed.
  • Use Get-GraphGatewayRunnerStatus.ps1 to inspect runner discovery and auth readiness.
  • Use get-graph-gateway-runner-status.sh on macOS or Linux when pwsh is installed.
  • Use Install-MsGraphRunner.ps1 to bootstrap the preferred merill/msgraph runner into the workspace when you explicitly want local setup.
  • Use New-GraphEventResponseRequest.ps1 to generate accept, decline, and tentative meeting-response requests.
  • Use New-GraphGatewayAppConfig.ps1 to generate environment snippets for a tenant-approved custom app registration.

Example Assets

  • Read Mail Request
  • Send Mail Request
  • List Events Request
  • Create Event Request
  • Accept Event Request
  • Decline Event Request
  • Tentative Event Request
  • Custom App Env Example

Done Criteria

  • The request was routed to WorkIQ or Microsoft Graph for an explicit reason.
  • Graph calls used least-privileged intent and minimal response shape where practical.
  • Writes were confirmed before execution.
  • Deletes were blocked or separately escalated.
  • The response states what happened and any remaining risk or next action.

References

  • Capability Matrix
  • Routing And Safety
  • Substrate Selection
  • Raw Execution Contract
  • Permission Profiles
  • Curated Tools First Wave
  • Environment Setup
  • Prerequisites
  • Troubleshooting

Related skills

FAQ

When does it use Graph vs workIQ?

workIQ for common reads (inbox, meetings, file discovery); Microsoft Graph for all writes and gap-reads needing exact endpoints, $select/$filter or directory data.

How are writes handled?

Send, create, update, move, upload, reply and assign are treated as writes and require explicit confirmation; deletes are disabled by default or behind stronger confirmation.

Automation & Workflowsintegrationsbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.