Guides the Copilot CLI on how to use the WorkIQ CLI/MCP server to query Microsoft 365 Copilot data (emails, meetings, docs, Teams, people) for live context, summaries, and recommendations.
WorkIQ (Public Preview) lets Copilot query Microsoft 365 data with natural language. It supports schedules, documents, Teams messages, email threads, follow-up tracking, stakeholder summaries, and more. Use this skill whenever a task needs live organizational intelligence beyond the local repository.
Supported Data & Sample Prompts
Emails – “Summarize emails from Sarah about the budget.”
Meetings – “What are my upcoming meetings this week?”
Documents – “Find recent documents about Q4 planning.”
Teams – “Summarize messages in the Engineering channel today.”
People/Projects – “Who is working on Project Alpha?”
Getting Access
Copilot CLI plugin (preferred)
copilot
/plugin marketplace add github/copilot-plugins
/plugin install workiq@copilot-plugins
Restart Copilot CLI.
Standalone CLI / MCP server
npm install -g @microsoft/workiq (or ).
npx -y @microsoft/workiq mcp
Run workiq mcp to expose MCP tools if needed.
Tenant consent
First use prompts for Microsoft 365 admin consent (EULA + permissions). Non-admins must contact tenant admin to approve per the Tenant Administrator Enablement Guide.
Pre-flight Checklist
Run Get-Command workiq to ensure the binary is available.
Accept the EULA once via workiq accept-eula.
Confirm the correct tenant (-t <tenant-id> if different from default common).
Be ready to complete device login in the browser when prompted.
Core Workflow
Clarify intent – agenda, action items, document lookup, people search, risk summary, etc.
Craft precise prompt – include timeframe, source, or topic (e.g., “Summarize Teams posts in #eng for today”).
Run command – workiq ask --question "<prompt>" (use -q for shorthand if desired).
Monitor execution – long answers may stream; wait for the response to finish before issuing additional requests.
Respect privacy: do not expose attendee lists or confidential snippets unless explicitly requested.
Log which commands were run so future steps can reference them (“Asked WorkIQ for agenda + conflicts”).
Use MCP mode (workiq mcp) when another agent/workflow needs direct tool access.
Troubleshooting
Missing CLI – install via npm or ensure PATH is set; notify user if unavailable.
Consent/auth errors – re-run command after admin grants permissions or after completing device login.
Long/incomplete output – rerun with refined scope or ask for specific data slices (per day/project/person).
Command hanging – cancel the running command in your terminal (for example, with Ctrl+C) or restart the Copilot CLI session, then retry; ensure browser login completed.
