microsoft/install-atk
plugins/microsoft-365-agents-toolkit/skills/install-atk/SKILL.md
Install or update the M365 Agents Toolkit (ATK) CLI and VS Code extension. Triggers: "install atk", "update atk", "install agents toolkit", "update agents toolkit", "install the toolkit", "setup atk", "get atk", "install atk cli", "install atk extension", "install atk vsix", "update the vs code extension", "install latest atk", "upgrade atk"
$ install --global
skillsauthnpx skillsauth add microsoft/work-iq install-atkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 16, 2026, 6:28 AM222.9s1 file scanned
SKILL.md
- name:
- install-atk
- description:
- >
- Triggers:
- install atk", "update atk", "install agents toolkit", "update agents toolkit",
Install ATK
Install or update the M365 Agents Toolkit (ATK) CLI and/or VS Code extension.
Telemetry Tagging
Before running any atk CLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated:
export ATK_CLI_SKILL=true
Run this once at the start of the session. All subsequent atk commands in the same terminal will inherit it.
Triggers
This skill activates when the user asks to:
- Install or update ATK / Agents Toolkit / the toolkit
- Install or update the ATK CLI
- Install or update the ATK VS Code extension / VSIX
- Set up ATK / get started with ATK
Behavior
ATK CLI commands use npx -y --package @microsoft/m365agentstoolkit-cli atk which automatically downloads and runs the latest version — no global installation is needed.
When triggered, determine what the user wants:
| User intent | Action | |-------------|--------| | Install/update everything or just "ATK" | Verify CLI works + install VSIX | | Install/update CLI only | Verify CLI works (npx handles it automatically) | | Install/update extension / VSIX only | Install VSIX only | | Ambiguous | Verify CLI works + install VSIX |
Commands
Step 1: Verify ATK CLI works
npx -y --package @microsoft/m365agentstoolkit-cli atk --version
- If this succeeds (prints a version): ATK CLI is available. The
npxprefix automatically downloads the latest package on first use and caches it for subsequent runs. - If this fails: Check that Node.js 18+ and npm are installed. The
npxcommand requires a working Node.js environment.
Step 2: ATK VS Code Extension (if requested)
code --install-extension TeamsDevApp.ms-teams-vscode-extension
Execution
- Verify ATK CLI works by running
npx -y --package @microsoft/m365agentstoolkit-cli atk --version - Report the result (version number / failure)
- Install VS Code extension if requested
- Explain that all ATK commands use the
npx -y --package @microsoft/m365agentstoolkit-cli atkprefix — no global install needed
Safety Rules
- MUST NOT skip errors — report failures clearly to the user
- MUST use the exact package names and extension IDs above — do not substitute with other names or links
Related Skills
microsoft/slack-to-teams
tools
VerifiedTrustedCommunity
Sub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams development without Slack (use parent skill instead).
841SKILL.mdUpdated May 30, 2026
microsoft/teams-app-developer
tools
VerifiedTrustedCommunity
Build, test, and deploy code-based Teams apps using the M365 Agents Toolkit CLI. USE FOR: Custom Engine Agents (CEA), Teams bots, tabs, message extensions, Agents Playground local testing, Azure provision/deploy, Slack-to-Teams migration, cross-platform bot development, Block Kit to Adaptive Cards conversion, AI model integration (OpenAI/Azure/Anthropic/Bedrock). DO NOT USE FOR: declarative agents — use the `declarative-agent-developer` skill instead. Triggers: "build a teams bot", "custom engine agent", "CEA", "teams agent", "tab app", "message extension", "test with agents playground", "provision to azure", "deploy to azure", "migrate slack bot", "slack to teams", "convert block kit", "add azure openai to my bot"
841SKILL.mdUpdated May 30, 2026
microsoft/plugins/workiq-preview/skills/workiq-preview
tools
VerifiedTrustedCommunity
--- name: workiq-preview description: Preview build of WorkIQ — the full Microsoft 365 tool surface: agentic semantic queries via ask_work_iq PLUS direct, structured reads and writes for emails, meetings, calendar, documents, Teams messages, OneDrive/SharePoint files, and people. USE THIS SKILL for ANY workplace question or write action where the data lives in Microsoft 365. Read triggers, "what did [person] say", "what are [person]'s priorities", "top of mind from [person]", "what was discussed
838SKILL.mdUpdated May 26, 2026
microsoft/workiq
development
VerifiedTrustedCommunity
Query Microsoft 365 Copilot for workplace intelligence - emails, meetings, documents, Teams messages, and people information. USE THIS SKILL for ANY workplace-related question where the answer likely exists in Microsoft 365 data. This includes questions about what someone said, shared, or communicated; meetings, emails, messages, or documents; priorities, decisions, or context from colleagues; organizational knowledge; project status; team activities; or any information that would be in Outlook, Teams, SharePoint, OneDrive, or Calendar. When in doubt about workplace context, try WorkIQ first. Trigger phrases include "what did [person] say", "what are [person]'s priorities", "top of mind from [person]", "what was discussed", "find emails about", "what meetings", "what documents", "who is working on", "what's the status of", "any updates on", etc.
807SKILL.mdUpdated May 16, 2026