Skip to content
AI-SKILLS

WorkIQ Copilot

👤 Github
•
📅 January 30, 2026
•
⭐ 19.5K
View on GitHub →

Introduction

The WorkIQ Copilot skill bridges the gap between your development environment and your organizational data. It enables the Copilot CLI and Claude to query Microsoft 365 (emails, meetings, documents, Teams, and people) using natural language.

By integrating this skill, you can access live context beyond your local repository, making it an essential tool for developers who need to manage schedules, track stakeholder communications, or summarize project documentation without leaving the terminal.

Key Features:

  • Unified Search: Query across Emails, Teams, and SharePoint documents simultaneously.
  • Actionable Insights: Extract follow-up items, summarize meeting notes, and identify project blockers.
  • MCP Integration: Includes a built-in Model Context Protocol (MCP) server to expose tools to other AI agents.
  • Privacy Focused: Operates within your tenant’s security boundaries and requires explicit admin consent.

Installation

You can set up WorkIQ via the Copilot CLI plugin marketplace or as a standalone Node.js package.

Install the plugin directly within your Copilot environment:

Terminal window
copilot
/plugin marketplace add github/copilot-plugins
/plugin install workiq@copilot-plugins

2. Standalone CLI & MCP Server

If you prefer using the tool via npx or as a global package:

Terminal window
npm install -g @microsoft/workiq

3. Pre-flight Setup

Before your first use, you must accept the EULA and ensure your system recognizes the binary:

  1. Verify installation: Get-Command workiq or which workiq
  2. Accept the license: workiq accept-eula
  3. Tenant Consent: Your first query will prompt for Microsoft 365 admin consent. Follow the browser-based device login instructions to authenticate.

Usage

WorkIQ is designed for natural language interaction. Use the ask command to query your M365 data.

Core Commands

CommandPurpose
workiq ask -q "..."Ask a specific question about your M365 data.
workiq mcpStart the MCP stdio server for tool-calling agents.
workiq versionCheck the current version.

Example Prompts

  • Meetings: "What are my upcoming meetings this week?"
  • Summarization: "Summarize follow-ups from today's customer sync."
  • Document Search: "Find recent PowerPoints about the Q4 roadmap."
  • Communication: "What did my manager say about the project deadline in Teams?"

Tip: Use the -t <tenant-id> flag if you need to target a specific Microsoft 365 tenant other than your default.

Best Practices

To get the most out of WorkIQ Copilot, follow these guidelines:

  • Be Specific: Instead of “Show me emails,” try “Summarize emails from Sarah about the budget sent this week.”
  • Combine Context: Ask WorkIQ to look for conflicts and suggest focus blocks in a single workflow.
  • Respect Privacy: Avoid requesting raw attendee lists or confidential snippets unless necessary for the task at hand.
  • Streamline Workflow: Use the workiq mcp mode when you want Claude to have direct, programmatic access to these tools during a coding session.

Troubleshooting

  • Command Hanging: If a request hangs, use Ctrl+C to cancel. Ensure your browser login is fully completed.
  • Missing CLI: Ensure the npm global bin directory is in your system PATH.
  • Consent Errors: If you receive a permissions error, contact your IT administrator to approve the WorkIQ application in your Microsoft 365 tenant.
  • Refining Scope: If output is too long or hits token limits, refine your query to a specific time range (e.g., “just for yesterday”) or a specific person.