flowstate-connector-microsoft-365 Package Skill

Package: @epicdm/flowstate-connector-microsoft-365 Repository: epic-flowstate-community Path: packages/flowstate-connector-microsoft-365 Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

FlowState Connector Microsoft 365 Auth

Status: Active Purpose: Configure Microsoft Graph OAuth for the Outlook connector. Scope: connector.yaml, README, Microsoft 365 setup runbook, Entra app settings. Trigger: New connector setup, token exchange errors, scope changes, redirect URI changes. Input: Entra app registration, callback URL, connector env vars. Output: OAuth setup compatible with connector-core.

Required Env Vars

MICROSOFT_365_CLIENT_ID=...
MICROSOFT_365_CLIENT_SECRET=...
MICROSOFT_365_REDIRECT_URI=...

Use the same callback URL in the Entra app registration and connector service env.

OAuth Contract

Package manifest:

authorizationUrl: https://login.microsoftonline.com/common/oauth2/v2.0/authorize
tokenUrl: https://login.microsoftonline.com/common/oauth2/v2.0/token
pkce: true

The bundled connector-core manifest currently uses a tenant-specific URL. Review tenant policy before changing either file.

Scope Checklist

• offline_access
• openid
• profile
• User.Read
• Mail.ReadWrite
• Mail.Send
• Calendars.ReadWrite

Mail.Send is for the action endpoint. Do not remove it just because scheduled sync is pull-only.

Operator Path

flowstate plugin install flowstate-connector-microsoft-365
flowstate connector connect microsoft-365
flowstate connector list --json

Verification

yarn workspace @epicdm/flowstate-connector-microsoft-365 test

Created: 2026-06-30

Package Skill Inventory

@epicdm/flowstate-connector-microsoft-365 Skill Inventory

These skills are grouped by agent/operator workflows, not by the two manifest files detected by the generated feature inventory.

API passthrough and operations troubleshooting are covered by the delta-sync, send-mail, auth, and maintenance skills rather than a separate broad catch-all.

Review Gate

@epicdm/flowstate-connector-microsoft-365 Skill Review

Created package-local skills for Microsoft 365 Outlook under packages/flowstate-connector-microsoft-365/.flowstate/skills.

Evidence Reviewed

• package.json
• README.md
• connector.yaml
• flowstate.plugin.json
• __tests__/connector.test.ts
• docs/runbooks/microsoft-365-connector-setup.md
• packages/connector-core/manifests/microsoft-365.yaml
• Connector-core bundled manifest and runtime tests for Microsoft 365 delta/action behavior
• .flowstate/feature-matrix/inventory.md
• .flowstate/dojo/agent-skillset.md

Review Notes

• No JS/TS public exports exist.
• The connector is pull-only for sync but has an action-only send-mail passthrough endpoint.
• Graph sync depends on OData nextLink, full URL deltaLink, and providerConfig _delta persistence.
• Calendar sync requires calendarStartDateTime and calendarEndDateTime.
• The bundled connector-core manifest intentionally differs from the package manifest and must be reviewed during maintenance.
• Generated Dojo material may be catalog-valid or marked published, but is generic and not content-ready.
• Known operational failures to teach: Graph 403/admin consent, 429 throttling, redirect mismatch, expired client secret, bad stored delta URL, and vault/token storage failures.

Verification Status

• ASCII scan passed: no non-ASCII characters in .flowstate/skills.
• Skill frontmatter scan passed for all 6 SKILL.md files.
• yarn workspace @epicdm/flowstate-connector-microsoft-365 test passed: 1 suite, 6 tests.
• yarn workspace @epicdm/flowstate-connector-microsoft-365 build passed; build is a no-op by design.
• yarn nx build @epicdm/flowstate-connector-microsoft-365 passed; Nx Cloud reported the existing unconnected-workspace 401 notice.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-connector-microsoft-365/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.