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