skill-m365-copilot-chat

Query Microsoft 365 Copilot web UI with Playwright MCP for grounded responses.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tobiascm/vobes-agent-vscode --skill skill-m365-copilot-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-m365-copilot-chat
Source: https://github.com/tobiascm/vobes-agent-vscode/tree/main/.agents/skills/skill-m365-copilot-chat
Command: npx skills add https://github.com/tobiascm/vobes-agent-vscode --skill skill-m365-copilot-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates getting answers from Microsoft 365 Copilot through the web UI using Playwright MCP, eliminating token transfers and Python HTTP calls while preserving user-initiated, browser-based interactions.

Core Features & Use Cases

  • Playwright MCP-driven Copilot chat: send prompts and read responses from the web UI.
  • Supports initial prompts and follow-ups within the same Copilot conversation.
  • Grounded results from Copilot's UI with no external API calls required.

Quick Start

Open the Copilot web UI and send your first prompt using Playwright MCP to receive a Copilot response.

Frequently Asked Questions about skill-m365-copilot-chat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Microsoft 365 Copilot chat through the web UI?

Automate Microsoft 365 Copilot chat by using Playwright MCP to interact directly with the web UI DOM, sending prompts and reading responses without Python HTTP clients or API tokens.

Can I send follow-up questions in the same Copilot conversation using Playwright?

Yes, you can send follow-up questions in the same Copilot conversation using Playwright MCP, which maintains the chat session context within the browser for grounded responses.

Do I need API tokens to query M365 Copilot via browser automation?

No, you do not need API tokens to query M365 Copilot via browser automation. Playwright MCP uses DOM interaction on an active M365 web session, entirely eliminating token transfers.

What is the best way to get M365-grounded responses without external API calls?

The best way to get M365-grounded responses without external API calls is using Playwright MCP for browser-based DOM interaction to query the Copilot web UI directly.

Why should I use DOM interaction instead of a Python HTTP client for Copilot chat?

Use DOM interaction instead of a Python HTTP client to preserve user-initiated browser sessions and avoid token management, leveraging Playwright MCP for direct UI automation.

What are the limitations of using Playwright MCP for M365 Copilot chat?

Using Playwright MCP for M365 Copilot chat requires an active M365 web session and is limited to UI DOM interactions, meaning it depends on browser stability and cannot bypass web UI constraints.