| name | orchestrator |
| description | USE FOR: Generate, change, or extend modular, minimal Microsoft Graph SDK apps for a use case. Identify requirements, resolve endpoints, generate SDK, write app code, and provide run instructions.
DO NOT USE FOR: Non-Microsoft Graph scenarios.
INVOKES: endpoint-resolver, generate-sdk-kiota, generate-sdk-ai, write-app-code.
|
Orchestrator
Generate, change, or extend modular, minimal Microsoft Graph SDK applications for a use case.
1. Determine project context
Determine the following requirements. Ask user only when details cannot be inferred from prompt or file context:
- New or existing project
- Use Case
- Language and Framework
- Delegated or Application permissions
- Authentication flow
- v1.0 or beta version
Summarize requirements and wait for confirmation. After approval, scaffold the project for the language/framework.
Best Practices
Authentication flow
| Scenario | Flow/Grant |
|---|
| Single Page App | Authorization Code with PKCE (delegated) |
| Background service | Client Credentials (app) |
| Web app | Authorization Code (delegated) or Client Credentials (app) |
| Web API | On Behalf Of (delegated) or Client Credentials (app) |
| Desktop app | Interactive or Device Code (delegated) |
| Mobile App | Interactive (delegated) |
API version policy
| Policy | Recommendation |
|---|
v1.0 | Production and stable scenarios (default) |
beta | Only when requested, communicate that APIs may change without notice. |
2. Identify API endpoints
Call endpoint-resolver to determine endpoints and permissions.
3. Generate SDK
- Call
generate-sdk-kiota by default.
- Call
generate-sdk-ai if an ai-generated SDK is explicitly stated.
4. Write application code
Call write-app-code skill after generating the SDK.
5. Provide instructions
Provide setup and run instructions with all four sections below.
- Register the application and other resources in Entra ID portal
- Select and consent to permissions
- Obtain authentication configuration
- Run the application locally
