Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of model-apps telemetry or its usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add microsoft/power-platform-skills --skill telemetry --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Telemetry?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/microsoft-telemetry-power-platform-skills)More formats (shields.io, HTML) on the badges page.
---
name: telemetry
description: >
Use this skill when the user wants to enable, disable, turn on or off, opt out
of, opt in to, or check the status of model-apps telemetry or its usage
data. Triggers: "disable telemetry", "turn off telemetry", "opt out of
telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
user-invocable: true
argument-hint: "on | off | status"
allowed-tools: Bash
model: haiku
---
> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding.
**Workflow: [telemetry-workflow.md](${PLUGIN_ROOT}/skills/telemetry/telemetry-workflow.md)** — Read and follow all steps defined in that bundled file.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
