WorkIQ

Query Microsoft 365 data (emails, meetings, documents, Teams messages, people) using WorkIQ CLI

Security Scan

The skill's requests and runtime instructions align with its stated purpose (invoking the WorkIQ CLI to query Microsoft 365 data); no unrelated credentials or suspicious install sources are requested, though the SKILL.md suggests using npx which will run remote code unless the CLI is installed locally.

Purpose & Capability

The skill states it queries Microsoft 365 via the WorkIQ CLI and the instructions require either the 'workiq' binary or 'npx' to run @microsoft/workiq. Those requirements match the described capability. Minor inconsistency: registry name appears as "WorkIa" while SKILL.md and metadata use 'workiq'.

Instruction Scope

SKILL.md only instructs the agent to run the WorkIQ CLI (or npx fallback), accept EULA, and handle common CLI errors. It does not ask the agent to read unrelated files, environment variables, or send data to third‑party endpoints. It correctly notes that interactive sign-in is required and that the user must complete it manually if prompted.

Install Mechanism

There is no install spec in the registry (instruction-only). The doc recommends 'npm install -g @microsoft/workiq' or using 'npx -y @microsoft/workiq' as a fallback. Installing from npm or invoking via npx is expected for this CLI; however, npx runs remote package code on demand, which increases transient execution risk compared with a preinstalled, pinned binary.

Credentials

The skill declares no required environment variables or credentials. This is proportionate: authentication is delegated to the WorkIQ CLI's interactive sign-in flow and to whatever account the user has already authenticated with.

Persistence & Privilege

The skill is not marked 'always' and does not request persistent system configuration. It will invoke local CLI binaries via exec when used. Allowing the agent to invoke the skill autonomously is platform-default; there are no additional elevated privileges requested.

Assessment

This skill is coherent with its stated purpose, but review these practical points before installing: 1) The skill runs the WorkIQ CLI locally (or via npx). If you don't already trust the @microsoft/workiq package, prefer to install a vetted version yourself (npm install -g @microsoft/workiq) instead of using npx, which executes remote code on-demand. 2) Authentication is interactive: the agent cannot complete the sign-in for you — you'll need to run workiq ask manually to sign in and accept the EULA. 3) The skill does not request extra credentials, but when you run the CLI it will access Microsoft 365 data that the signed-in account can see—install and run only if you trust the CLI and the environment. 4) Note the small name mismatch between the registry entry and SKILL.md ("WorkIa" vs "workiq"); that's likely a metadata typo but verify you are installing the expected skill.

WorkIQ — Microsoft 365 Data Query

Use this skill to answer questions about Microsoft 365 data: emails, meetings, calendar, documents, Teams messages, and people/org insights. WorkIQ queries data the authenticated user already has permission to access — no extra permissions are granted.

When to use

Invoke this skill whenever the user asks about:

• Emails — "What did Sarah say about the budget?", "Find emails about project X"
• Calendar / meetings — "What's on my calendar tomorrow?", "Who attended the standup last Friday?"
• Documents / files — "Find my recent PowerPoints", "Summarize the Q4 spec document"
• Teams messages — "Summarize today's messages in the Engineering channel"
• People / org — "Who is working on Project Alpha?", "Who is my manager?"
• Meeting notes — "What issues were raised in yesterday's Contoso meeting?"

How to query

Use the exec tool to run WorkIQ. Prefer the global CLI if available, otherwise fall back to npx.

If workiq is on PATH:

workiq ask -q "<natural language question>"

If only npx is available (Node.js required):

npx -y @microsoft/workiq ask -q "<natural language question>"

With a specific Entra tenant ID:

workiq ask -t <tenant-id> -q "<natural language question>"

Query guidelines

• Write questions in natural language — WorkIQ understands context
• Be specific: include names, dates, project names, or channel names when known
• WorkIQ CLI is stateless per call — for follow-ups, include full context in each question
• WorkIQ only returns data the signed-in user has permission to see
• Do not pipe or combine WorkIQ output with other shell commands — run it standalone

Example queries

User intent	Command
Recent emails on a topic	workiq ask -q "What did John say about the proposal last week?"
Tomorrow's calendar	workiq ask -q "What meetings do I have tomorrow?"
Find a document	workiq ask -q "Find my recent documents about Q4 planning"
Teams channel summary	workiq ask -q "Summarize today's messages in the Engineering channel"
People lookup	workiq ask -q "Who is working on Project Alpha?"
Meeting notes	workiq ask -q "What issues were raised in yesterday's Contoso meeting?"
Spec document	workiq ask -q "Summarize the key requirements in the user portal spec document"
Emails from a person	workiq ask -q "Summarize emails from Sarah about the budget"

First-time setup

If WorkIQ has never been used, the EULA must be accepted first. Tell the user to run:

workiq accept-eula

If WorkIQ is not installed at all:

npm install -g @microsoft/workiq
workiq accept-eula

Error handling

Error	Action
Auth / sign-in prompt	Tell the user to run workiq ask manually in their terminal to complete the interactive sign-in flow
EULA not accepted	Prompt the user to run workiq accept-eula
No results / empty response	Rephrase the question with more context, a different time range, or more specific names
Permission denied	User may lack an M365 Copilot license or admin consent for the WorkIQ app in their Entra tenant
workiq not found	Prompt the user to install: npm install -g @microsoft/workiq