Agent skill · software engineering · github
msgraph-sdk
Integrate Microsoft Graph SDK into any project — .NET, TypeScript/JavaScript, or Python. Covers auth patterns (client credentials, OBO, managed identity), SDK setup, calling Graph APIs, batching, delta queries, change notifications, throttling, and permission scopes. Use when accessing Microsoft 365 data (users, mail, calendar, Teams, files, SharePoint) from any application type.
Why this skill is useful
Provides specific authentication patterns and SDK usage examples for integrating with Microsoft Graph that the AI wouldn't reliably generate on its own.
What it needs
Requires dotnet, npm, python installed locally. Requires microsoft account access. About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Microsoft Graph SDK Use this skill when integrating Microsoft Graph into an application to access Microsoft 365 data and services. Always ground implementation in the current Microsoft Graph SDK documentation and SDK version for the target language rather than relying on memory alone. Determine the target language first 1. Use the .NET workflow when the project contains .cs, .csproj, or .sln files, or when the user asks for C# guidance. Follow references/dotnet.md. 2. Use the TypeScript / JavaScript workflow when the project contains package.json, .ts, or .js files, or when the user asks for Node.js / browser guidance. Follow references/typescript.md. 3. Use the Python workflow when the project contains .py, pyproject.toml, or requirements.txt, or when the user asks for Python guidance. Follow references/python.md. 4. If multiple languages are present, match the language of the files being edited or ask the user. Always consult live documentation Microsoft Graph overview: <https://learn.microsoft.com/graph/overview> Graph Explorer (try calls live): <https://developer.microsoft.com/graph/graph-explorer> Graph permissions reference: <https://learn.microsoft.com/graph/permissions-reference> Use Microsoft Docs MCP tooling when available to fetch current API shapes and SDK samples. Authentication — choose the right pattern Selecting the wrong auth flow is the most common Graph integration mistake. Apply this decision tree before writing any auth code: Scenario Flow to use --- --- Background service / daemon with no user Client credentials (app-only) Agent or API acting on behalf of a signed-in user On-Behalf-Of (OBO) App running in Azure (Function, Container App, VM) Managed Identity (preferred over secrets) CLI tool or local dev script Device code or interactive browser Single-page app (browser only) Authorization code + PKCE Never use client credentials when a user context is required — Graph enforces this at the permission level (application vs. delegated). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/msgraph-sdk