graph
Skill2 starsChanged 3 months agoMITView on GitHub
Use this skill for unattended Microsoft Graph automation with app-only authentication, sovereign cloud awareness, pagination, and throttling-aware REST calls.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- artemnovitckii/claude-animation-skillstheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- renzrollon/interlocktheir own version, first seen Nov 5, 2026
- iwe-org/skillstheir own version, first seen Nov 1, 2026
- zbsaygin/econ-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use understand, ingest and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agoodwaySkillunderstand
Multi-specialist collaborative analysis to understand how features, functions, or components work
Also in 3 projects that use this
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 4 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
MicrosoftSkillinit
Also in 3 projects that use this
AnthropicSkillstart
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
Also in 3 projects that use this
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- atopile/atopile★ 4ksame name
- ZimoLiao/scholaraio★ 585same name
- artemnovitckii/claude-animation-skills★ 500same name
- smallnest/goal-workflow★ 283same name
- romarayt/raytsystem-public-os★ 140same name
- renzrollon/interlock★ 61same name
- ratomirjovanovic/pandaward★ 50same name
- drafthq/draft★ 40same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- agents.mdAGENTS.md
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- azureSkill
- copilotstudioSkill
- dataverseSkill
- intuneSkill
- loganalyticsSkill
- powerplatformSkill
- sentinelSkill
- sharepoint-onlineSkill
- teamsSkill
- vm-guest-managementSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Use this skill when an agent needs Microsoft Graph app-only automation without interactive sign-in.
- Distinctive: line 26
Run the same automation in Azure commercial, US Gov, or China clouds.
- Distinctive: line 27
Follow Graph pagination and handle throttling without reimplementing retry logic.
- Very specific: line 63
Prefer ManagedIdentity or Federated authentication.
- Distinctive: line 64
Never assume delegated/user auth is available.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Microsoft Graph Skill
Agent Summary
Use this skill when an agent needs Microsoft Graph app-only automation without interactive sign-in. Start by creating a context with Connect-GraphApi.ps1, then send relative Graph paths or absolute @odata.nextLink URLs to Invoke-GraphRequest.ps1.
When to Use
- Query Microsoft Entra ID objects such as users, groups, applications, or service principals.
- Run the same automation in Azure commercial, US Gov, or China clouds.
- Follow Graph pagination and handle throttling without reimplementing retry logic.
Required Parameters
Connect-GraphApi.ps1
| Parameter | Type | Required | Notes |
AuthenticationType | string | Conditional | ManagedIdentity, Federated, Certificate, or ClientCredentials. |
Environment | string | No | Defaults to AzureCloud. |
TenantId | string | Conditional | Required for Federated, Certificate, and ClientCredentials. |
ClientId | string | Conditional | Required for Federated, Certificate, and ClientCredentials; optional for user-assigned managed identity. |
FederatedToken | string | Conditional | Required for Federated. |
CertificatePath | string | Conditional | Required for Certificate. |
ClientSecret | SecureString | Conditional | Required for ClientCredentials. |
Invoke-GraphRequest.ps1
| Parameter | Type | Required | Notes |
Uri | string | Yes | Relative Graph path or absolute nextLink URL. |
AuthContext | hashtable | Yes | Output from Connect-GraphApi.ps1. |
Method | string | No | Defaults to GET. |
Body | object | No | Request payload for writes. |
Paginate | switch | No | Aggregate @odata.nextLink pages. |
Example Agent Prompts
- "List all Microsoft Graph users with
id,displayName, andmail." - "Get a specific group from Microsoft Graph by ID using app-only auth."
- "Follow all pages for a Graph query and return the aggregated results."
Example Agent Workflow
$context = ./skills/graph/Connect-GraphApi.ps1 -AuthenticationType ManagedIdentity -Environment AzureCloud
$users = ./skills/graph/Invoke-GraphRequest.ps1 -AuthContext $context -Uri "/users?`$select=id,displayName,mail" -PaginateSecurity Caveats
- Prefer
ManagedIdentityorFederatedauthentication; use client secrets only as a last resort. - Never assume delegated/user auth is available; this skill is designed for app-only execution.
- Grant only the minimum Graph application permissions required for the requested operation.
Overview
This skill domain covers unattended Microsoft Graph API automation using app-only authentication. It provides a standardized way to acquire Graph tokens for different Azure environments and invoke Graph REST requests with pagination and throttling-aware retries.
Authentication
- Which auth types work for Graph: ManagedIdentity, Federated, Certificate, ClientCredentials
- Token audience: https://graph.microsoft.com (or AzureUSGovernment: https://graph.microsoft.us, AzureChinaCloud: https://microsoftgraph.chinacloudapi.cn)
- Graph-specific auth notes: app-only context only. These scripts acquire tokens using the Graph resource endpoint with the default scope, and they do not implement delegated (user) flows.
Endpoints
| Environment | Graph Endpoint |
| AzureCloud | https://graph.microsoft.com |
| AzureUSGovernment | https://graph.microsoft.us |
| AzureChinaCloud | https://microsoftgraph.chinacloudapi.cn |
Skills
| File | Purpose |
| Connect-GraphApi.ps1 | Resolves the selected Azure environment and returns a Graph auth context (token, expiry, Graph endpoint, and BaseUri) suitable for Invoke-GraphRequest. |
| Invoke-GraphRequest.ps1 | Invokes Microsoft Graph REST requests (relative Graph paths or absolute nextLink URLs), with optional @odata.nextLink pagination aggregation and throttling-aware retries. |
| auth/*.ps1 | Token acquisition wrappers for each supported auth type (ManagedIdentity, FederatedCredentials, CertificateBased, ClientCredentials), producing a Graph authentication context. |
Toolchain
| Tool | Best For | Token Audience | Limitations in Graph Context |
Microsoft.Graph PowerShell SDK (Microsoft.Graph.*) | Rich Graph entity coverage, strong typing, pagination handled automatically | https://graph.microsoft.com/ (or gov/china equivalent) | Large module footprint; some beta endpoints lag behind REST API; app-only vs delegated context can be confusing |
Az PowerShell modules (Az.Accounts) | Token chaining from Azure context to Graph | https://graph.microsoft.com/ via Get-AzAccessToken -ResourceTypeName MSGraph | Limited to token acquisition; does not provide Graph SDK features |
Raw REST (Invoke-RestMethod) | Full control over Graph API versions (beta, v1.0), headers, and query parameters | https://graph.microsoft.com/ | Caller must handle pagination (@odata.nextLink), throttling (Retry-After), and token refresh manually |
Patterns & Caveats
- Pagination: Invoke-GraphRequest supports -Paginate, which follows @odata.nextLink (default) and aggregates the response payload from the value property.
- Throttling: Invoke-GraphRequest retries on HTTP 429 and 5xx responses, and it uses the Retry-After response header when present.
- $select usage: Put $select in the -Uri query to reduce response payload size, especially for list endpoints you plan to paginate.
- App-only context requirements: tokens are acquired for the Graph resource endpoint (https://graph.microsoft.com or the sovereign equivalent). When you call Invoke-GraphRequest, your app registration must have the required application permissions for the operations you perform.
Examples
# 1) Managed identity: list users with $select and pagination
$context = ./skills/graph/Connect-GraphApi.ps1 -AuthenticationType ManagedIdentity -Environment AzureCloud
$users = ./skills/graph/Invoke-GraphRequest.ps1 -AuthContext $context -Uri "/users?`$select=id,displayName,mail" -Paginate# 2) Federated credentials: get a single group
$context = ./skills/graph/Connect-GraphApi.ps1 `
-AuthenticationType Federated `
-TenantId $env:AZURE_TENANT_ID `
-ClientId $env:AZURE_CLIENT_ID `
-FederatedToken $env:AZURE_FEDERATED_TOKEN `
-Environment AzureCloud
$group = ./skills/graph/Invoke-GraphRequest.ps1 -AuthContext $context -Uri "/groups/$groupId?`$select=id,displayName"# 3) Use an absolute nextLink URL directly
$context = ./skills/graph/Connect-GraphApi.ps1 -AuthenticationType Certificate -TenantId $env:AZURE_TENANT_ID -ClientId $env:AZURE_CLIENT_ID -CertificatePath "/secure/certs/graph.pfx" -Environment AzureCloud
# First page (no aggregation)
$firstPage = ./skills/graph/Invoke-GraphRequest.ps1 -AuthContext $context -Uri "/users?`$select=id,displayName&`$top=1"
# Second page, calling Invoke-GraphRequest with the absolute nextLink URL
$secondPage = ./skills/graph/Invoke-GraphRequest.ps1 -AuthContext $context -Uri $firstPage."@odata.nextLink"# 4) Use a config.yaml profile
$context = ./skills/graph/Connect-GraphApi.ps1 -Profile "prod" -ConfigPath "./config.yaml"# 5) Use prefixed environment variables
$context = ./skills/graph/Connect-GraphApi.ps1 -Prefix "GOV" -Environment AzureUSGovernmentPrerequisites
- Required modules: the skill scripts require PowerShell 7.2+. For certificate-based token acquisition, MSAL.PS is used if available; otherwise the scripts fall back to Azure CLI (az) for the access token.
- Required permissions (application permissions): configure Microsoft Graph application permissions on the app registration used by your auth method. The scripts request tokens for the Graph resource endpoint and then call Graph with that token.
Related Docs
- Auth Patterns
- Token Chaining
- Environment Endpoints
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

