All skills
aktsmm avatar

/microsoft-graph-gateway

@848fd9b
by yamapanaktsmm/agent-skills26 stars
4

Route Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.

Use this Skill: https://skilld.dev/gh/aktsmm/agent-skills/microsoft-graph-gateway

This session only. Nothing lands on disk.

referencessubstrate-selection.md

≈422 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Substrate Selection

The gateway skill needs an execution substrate. This reference captures the current recommendation.

Recommended Core

merill/msgraph

Use as the primary generic Graph substrate when you need:

  • arbitrary endpoint reach
  • permission and schema lookup
  • direct Graph execution
  • strong write guardrails

Why it fits:

  • broad Graph coverage
  • explicit safety model for writes
  • strong discovery story for endpoints and permissions

Domain Helpers

elyxlz/microsoft-mcp

Best when you need curated productivity tools for:

  • mail
  • calendar
  • OneDrive
  • contacts
  • multi-account flows

XenoXilus/outlook-mcp

Best when you need curated productivity tools for:

  • Outlook mail
  • calendar
  • SharePoint links and files
  • attachment and document processing

Not A Primary Substrate

Microsoft MCP Server for Enterprise

Useful as a read-only supplement for directory and Entra questions, but not as the main execution substrate for Outlook and productivity writes.

VS Code Marketplace Extensions

Current marketplace candidates are mainly:

  • development helpers
  • autocomplete helpers
  • read-only viewers

They are not the recommended foundation for a full Graph gateway.

Current Recommendation

  1. Use merill/msgraph as the generic Graph core.
  2. Add a thin skill shell for routing, confirmation, and policy.
  3. Evaluate a productivity-focused MCP helper only where curated tools clearly improve operator experience.
  4. Consider a VS Code extension only after the gateway behavior is stable.

Operational Follow-Up

Source: SKILL.md on GitHub

1 alert4mo3 checks · Risk HIGH
  • Gen Agent Trust Hub4mo

    The skill acts as a gateway for Microsoft Graph, providing tools to read and write data across Microsoft 365. It includes functionality to download and execute an external runner tool from a third-party GitHub repository. While the skill implements some safety measures like write confirmation summaries and blocking delete operations, the practice of downloading and running external code at runtime from non-verified sources presents a significant security risk.

  • Socket4mo

    1 alert: gptAnomaly

  • Snyk4mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 848fd9b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago
user-invocable
true
metadata
{
  "author": "yamapan (https://github.com/aktsmm)"
}
Other metadata
argument-hint
Describe the Graph task, target resource, and any draft payload, endpoint, or constraints

README badge

README badge for aktsmm/agent-skills/microsoft-graph-gateway