telemetry · microsoft, power-automate — Claude Code skill: control Power Automate telemetry
telemetry is a Claude Code skill that toggles power-automate telemetry or reports its setting. It responds to requests to change the setting or inspect it.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-automate@power-platform-skillsWhat telemetry does
The skill changes the telemetry setting for the power-automate plugin or reports its status. The on, off, and status arguments select the action; status is used when no argument is supplied. A bundled configuration CLI runs through node.
The telemetry is pseudonymous and covers operational details such as skill and plugin versions, OS and Node versions, agent details, and Dataverse organization and Entra tenant identifiers. It excludes file paths, prompts, credentials, and error messages. Turning telemetry off stops transmission, but keeps the plugin’s local event log. Entries older than 14 days are pruned automatically.
A status check also prints the FlowAgent CLI/MCP local log path and whether that file exists; it does not determine whether an individual call is eligible for remote collection. The default path is ~/.flowagent/telemetry.jsonl. This separate log is not pruned automatically, and FLOWAGENT_TELEMETRY_LOG can override its location.
What it helps with
- turn off
power-automatetelemetry - enable plugin telemetry
- check the current telemetry setting
- find the FlowAgent CLI/MCP local log
Example prompts for the agent
- Turn off telemetry for
power-automate. - Enable telemetry for the plugin.
- Show the telemetry status and the FlowAgent log path.
How to install telemetry
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install power-automate@power-platform-skillsThis installs the whole power-automate plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill telemetry -a claude-code3Manually: put the files in place
~/.claude/skills/telemetry/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/telemetry/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill telemetry -a codex2Manually: put the files in place
.agents/skills/telemetry/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill telemetry -a cursor2Manually: put the files in place
.cursor/skills/telemetry/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/power-automate/skills/telemetry2Manually: put the files in place
.github/skills/telemetry/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill telemetry -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/power-automate/skills/telemetryManually: put the files in place
.devin/skills/telemetry/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about telemetry
How do I install telemetry in Claude Code?
Add the marketplace with /plugin marketplace add microsoft/power-platform-skills, then install the plugin with /plugin install power-automate@power-platform-skills.
What does telemetry do?
It switches telemetry for the power-automate plugin on or off and reports the setting. A status check also prints the FlowAgent CLI/MCP local log path.
What does telemetry need to run?
It needs Node to run the bundled configuration CLI and the power-automate plugin whose setting it controls.
Source text
SKILL.md · MIT
---
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 power-automate telemetry /
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
---
# Power Automate Telemetry Control
Enable, disable, or check the status of pseudonymous usage telemetry for the
`power-automate` plugin.
## What is collected
Telemetry is **pseudonymous**. It records operational fields — skill name,
plugin version, OS/Node versions, agent name/version, Dataverse organization
and Entra tenant IDs, and the signed-in user's Entra object ID when PAC exposes
it. It never includes file paths, prompts, tool inputs, flow names, URLs,
credentials, usernames, hostnames, or error messages. Plugin hook events have a
local diagnostic log, one file per session, under
`~/.power-platform-skills/telemetry/power-automate/sessions/<sessionId>/events.jsonl`
(nothing is transmitted when telemetry is OFF). Session logs older than 14 days
are pruned automatically. This hook log is separate from FlowAgent CLI/MCP
telemetry, whose local mirror is `~/.flowagent/telemetry.jsonl` by default
(`FLOWAGENT_TELEMETRY_LOG` overrides the path) and is not automatically pruned.
The status command below reports the plugin hook's setting and session logs;
it also prints the core log's path and whether the file exists, not whether a
particular CLI/MCP call is eligible for remote collection.
## Workflow
1. Determine the action from the user's request / `$ARGUMENTS`:
- `on` — opt in
- `off` — opt out (nothing transmitted; local log still kept)
- `status` (default) — report current state
2. Run the bundled config CLI and show its output verbatim:
```bash
node "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/lib/telemetry/lib/telemetry-config.js" --action <on|off|status> --plugin power-automate
```
For `status`, also show the FlowAgent CLI/MCP local log location:
```bash
node -e 'const fs = require("node:fs"); const os = require("node:os"); const path = require("node:path"); const log = process.env.FLOWAGENT_TELEMETRY_LOG || path.join(os.homedir(), ".flowagent", "telemetry.jsonl"); console.log(`FlowAgent CLI/MCP local log: ${log}${fs.existsSync(log) ? "" : " (not created yet)"}`);'
```
3. Confirm the result to the user in one sentence.
© Microsoft · MIT · microsoft/power-platform-skills
Similar skills
All skills for Automation and no-code: n8n, Zapier, Make →telemetry by other authors comes first.