add-workiq-tools

Add WorkIQ Tools (A365 CLI + SDK)

Trigger phrases — any of these will activate this skill automatically:

• "add workiq tools to this agent"
• "add work intelligence tools"
• "give this agent access to m365 data"
• "give my agent access to email and calendar"
• "add sharepoint access to this agent"
• "add work iq mail to this agent"
• "add work iq calendar to this agent"
• "let this agent read emails and calendar events"
• "wire up workiq MCP servers"

---

Overview

This skill adds WorkIQ MCP tool servers to an existing A365 agent using the A365 CLI.

WorkIQ tools give your agent pre-built access to M365 work data via MCP. The capability categories below describe what each catalog server does — but always pull the exact CLI argument names from a365 develop list-available. V2 catalog names look like mcp_MailTools, mcp_CalendarTools, etc., and they evolve over time.

• Mail — Read, send, and manage email
• Calendar — Read/create events, check availability
• Teams — Read channel messages, list teams
• SharePoint — Search documents, read files, list sites
• OneDrive — Manage OneDrive files
• Word — Read and write Word documents
• User/Presence — Get user profile and presence
• Copilot — Chat with Microsoft 365 Copilot
• Dataverse and Dynamics 365 — CRUD and domain actions

How it works:

1. a365 develop list-available — shows the catalog of available MCP servers
2. a365 develop add-mcp-servers — adds selected servers to ToolingManifest.json
3. Agent code is wired to load those tools at runtime via GetMcpToolsAsync
4. Permissions are applied separately by a developer or Global Administrator

All changes are additive and idempotent — rerunning is safe.

---

Phase 0A — Workspace Triage and Detection Cache

Step 1 — Triage the workspace

Run in parallel:

• Glob **/*.csproj, package.json, requirements.txt, pyproject.toml, src/**/*.ts, **/*.cs, **/*.py → hasProjectFiles.
• Read .a365-workspace-detection.local.json → cacheState (fresh if detectedAt < 60 min, stale if older, missing if absent).