WorkIQ Copilot Skill
Overview
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.
- Summarize & redact – highlight insights, note conflicts/tasks, avoid pasting raw links unless required.
- Offer follow-ups – blocking time, drafting notes, deeper queries, etc.
Command Reference
| Command |
Purpose |
workiq --help |
Show global options. |
workiq version |
Display installed version. |
workiq accept-eula |
Accept license (first use). |
workiq ask |
Interactive mode. |
workiq ask --question "..." |
Ask a specific question (use -q shorthand if preferred). |
workiq ask -t <tenant> -q "..." |
Target a specific tenant. |
workiq mcp |
Start MCP stdio server (expose WorkIQ tools to other agents). |
Prompt Patterns
- Agenda: “What’s on my calendar tomorrow?”
- Action items: “Summarize follow-ups from today’s customer sync.”
- Documents: “List PowerPoints about Contoso FY26 roadmap.”
- Communications: “What did my manager say about the deadline?”
- Insights: “What blockers came up in the last three meetings?”
- Planning: “Suggest focus blocks for Tuesday afternoon.”
Response Guidelines
- Keep summaries concise (2–3 sentences) calling out load, priorities, blockers, and optional next steps.
- Refer to meetings/documents generically unless the user specifically needs links.
- Mention if WorkIQ can continue (e.g., “WorkIQ can show Thu–Sun if needed”).
- Map WorkIQ’s suggested actions to clear offers (block time, send follow-up, request recording, run deeper query).
Best Practices
- Prefer narrow prompts to reduce noise; run multiple queries if needed.
- Combine outputs logically (agenda + conflicts + action items) before responding.
- 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.
Follow-up Actions to Offer
- Block focus/overflow holds at suggested times.
- Draft reschedule/decline messages referencing WorkIQ guidance.
- Request recordings or summaries for overlapping sessions.
- Capture action items into task trackers.
- Run additional WorkIQ queries (by project, stakeholder, time range) for deeper analysis.
Source: github/awesome-copilot → skills/workiq-copilot/SKILL.md
1---2name: workiq-copilot3description: 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.4---5# WorkIQ Copilot Skill67## Overview89WorkIQ (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.1011## Supported Data & Sample Prompts1213- **Emails** – “Summarize emails from Sarah about the budget.”14- **Meetings** – “What are my upcoming meetings this week?”15- **Documents** – “Find recent documents about Q4 planning.”16- **Teams** – “Summarize messages in the Engineering channel today.”17- **People/Projects** – “Who is working on Project Alpha?”1819## Getting Access20211. **Copilot CLI plugin (preferred)**22 - `copilot`23 - `/plugin marketplace add github/copilot-plugins`24 - `/plugin install workiq@copilot-plugins`25 - Restart Copilot CLI.262. **Standalone CLI / MCP server**27 - `npm install -g @microsoft/workiq` (or `npx -y @microsoft/workiq mcp`).28 - Run `workiq mcp` to expose MCP tools if needed.293. **Tenant consent**30 - First use prompts for Microsoft 365 admin consent (EULA + permissions). Non-admins must contact tenant admin to approve per the Tenant Administrator Enablement Guide.3132## Pre-flight Checklist3334- Run `Get-Command workiq` to ensure the binary is available.35- Accept the EULA once via `workiq accept-eula`.36- Confirm the correct tenant (`-t <tenant-id>` if different from default `common`).37- Be ready to complete device login in the browser when prompted.3839## Core Workflow40411. **Clarify intent** – agenda, action items, document lookup, people search, risk summary, etc.422. **Craft precise prompt** – include timeframe, source, or topic (e.g., “Summarize Teams posts in #eng for today”).433. **Run command** – `workiq ask --question "<prompt>"` (use `-q` for shorthand if desired).444. **Monitor execution** – long answers may stream; wait for the response to finish before issuing additional requests.455. **Summarize & redact** – highlight insights, note conflicts/tasks, avoid pasting raw links unless required.466. **Offer follow-ups** – blocking time, drafting notes, deeper queries, etc.4748## Command Reference4950| Command | Purpose |51| --------------------------------- | ------------------------------------------------------------- |52| `workiq --help` | Show global options. |53| `workiq version` | Display installed version. |54| `workiq accept-eula` | Accept license (first use). |55| `workiq ask` | Interactive mode. |56| `workiq ask --question "..."` | Ask a specific question (use `-q` shorthand if preferred). |57| `workiq ask -t <tenant> -q "..."` | Target a specific tenant. |58| `workiq mcp` | Start MCP stdio server (expose WorkIQ tools to other agents). |5960## Prompt Patterns6162- Agenda: “What’s on my calendar tomorrow?”63- Action items: “Summarize follow-ups from today’s customer sync.”64- Documents: “List PowerPoints about Contoso FY26 roadmap.”65- Communications: “What did my manager say about the deadline?”66- Insights: “What blockers came up in the last three meetings?”67- Planning: “Suggest focus blocks for Tuesday afternoon.”6869## Response Guidelines7071- Keep summaries concise (2–3 sentences) calling out load, priorities, blockers, and optional next steps.72- Refer to meetings/documents generically unless the user specifically needs links.73- Mention if WorkIQ can continue (e.g., “WorkIQ can show Thu–Sun if needed”).74- Map WorkIQ’s suggested actions to clear offers (block time, send follow-up, request recording, run deeper query).7576## Best Practices7778- Prefer narrow prompts to reduce noise; run multiple queries if needed.79- Combine outputs logically (agenda + conflicts + action items) before responding.80- Respect privacy: do not expose attendee lists or confidential snippets unless explicitly requested.81- Log which commands were run so future steps can reference them (“Asked WorkIQ for agenda + conflicts”).82- Use MCP mode (`workiq mcp`) when another agent/workflow needs direct tool access.8384## Troubleshooting8586- **Missing CLI** – install via npm or ensure PATH is set; notify user if unavailable.87- **Consent/auth errors** – re-run command after admin grants permissions or after completing device login.88- **Long/incomplete output** – rerun with refined scope or ask for specific data slices (per day/project/person).89- **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.9091## Follow-up Actions to Offer9293- Block focus/overflow holds at suggested times.94- Draft reschedule/decline messages referencing WorkIQ guidance.95- Request recordings or summaries for overlapping sessions.96- Capture action items into task trackers.97- Run additional WorkIQ queries (by project, stakeholder, time range) for deeper analysis.9899---100101**Source:** [`github/awesome-copilot`](https://github.com/github/awesome-copilot) → `skills/workiq-copilot/SKILL.md`