workiq-copilot_skill

This skill helps Copilot query Live Microsoft 365 data via WorkIQ to summarize emails, meetings, docs, and teams for actionable insights.
  • JavaScript
  • Official

19.4k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill github/awesome-copilot --skill workiq-copilot

  • SKILL.md5.4 KB

Overview

This skill guides the Copilot CLI to use the WorkIQ CLI/MCP server for querying Microsoft 365 Copilot data (emails, meetings, documents, Teams, people) to surface live context, summaries, and recommendations. It helps you connect, prompt, and interpret WorkIQ results so Copilot can act on organizational intelligence. Use it when you need up-to-date meeting context, follow-ups, or stakeholder summaries beyond the local repository.

How this skill works

The skill checks for the WorkIQ CLI or starts the MCP stdio server so other agents can call WorkIQ tools. It runs precise prompts via workiq ask (or the MCP server) to collect emails, calendar items, docs, Teams messages, and people/project info. Responses are summarized, redacted for privacy when needed, and returned as concise insights with suggested follow-ups or actions.

When to use it

  • Summarizing recent emails, meeting notes, or Teams channel activity.
  • Preparing for upcoming meetings with agenda, blockers, and priorities.
  • Finding recent documents or PowerPoints about a specific project or topic.
  • Identifying stakeholders, assignees, or people working on a project.
  • Generating follow-up actions and scheduling suggestions after syncs.

Best practices

  • Install and verify workiq CLI presence (Get-Command workiq) and accept the EULA before use.
  • Craft narrow prompts with timeframe, source, and topic to reduce noise (run multiple queries if needed).
  • Use MCP mode (workiq mcp) when a Copilot agent or workflow needs direct tool access.
  • Respect privacy: summarize generically and avoid exposing attendee lists or confidential snippets unless explicitly requested.
  • Log which workiq commands were run so responses and follow-ups can reference source queries.

Example use cases

  • "Summarize follow-ups from today’s customer sync and highlight blockers."
  • "What are my meetings and key priorities this week? Suggest focus blocks."
  • "Find recent PowerPoints about Q4 planning and summarize action items."
  • "Summarize Engineering channel messages for today and surface any decisions."
  • "Who is working on Project Alpha and what tasks are outstanding?"

FAQ

Install via npm (npm install -g @microsoft/workiq) or run with npx, then verify with Get-Command workiq and accept the EULA using workiq accept-eula.

What if I hit tenant consent or auth errors?

Tenant admin consent is required for Microsoft 365 access. Complete device login when prompted and have an admin approve permissions per the Tenant Administrator Enablement Guide; retry after consent is granted.

When should I use MCP mode instead of direct CLI calls?

Use workiq mcp when another agent or automated workflow needs direct programmatic access to WorkIQ tools over stdio; use single CLI commands for ad-hoc interactive queries.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
workiq-copilot skill by github/awesome-copilot | VeilStrat