telemetry
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".
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 1.1k
- Forks
- 229
01 前言 Front Matter
- name
- telemetry
- model
- haiku
- 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".
- allowed-tools
- Bash
- argument-hint
- on | off | status
- user-invocable
- true
03 SKILL.md 正文
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
-
Determine the action from the user's request /
$ARGUMENTS:on— opt inoff— opt out (nothing transmitted; local log still kept)status(default) — report current state
-
Run the bundled config CLI and show its output verbatim:
node "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/lib/telemetry/lib/telemetry-config.js" --action <on|off|status> --plugin power-automateFor
status, also show the FlowAgent CLI/MCP local log location: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)"}`);' -
Confirm the result to the user in one sentence.
04 同仓库更多 Skills
setup
Use when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.
report-issue
Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.
investigate-process
Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.
derive-metric
Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.
compare-cohorts
Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.
analyze-variants
Use when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.