telemetry · microsoft, power-apps-mobile-extension — Claude Code skill: switch usage telemetry on or off
Sets whether the Power Apps Mobile Extension skills send usage telemetry: on, off or status. Useful when you want out of collection or a quick look at the current setting.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-apps-mobile-extension@power-platform-skillsWhat telemetry does
Pass it on, off or status. The skill runs node "<plugin-root>/scripts/telemetry-config.js" --action <on|off|status> and prints the result unchanged. Leave the argument out, or give something unrecognised, and it falls back to status. A failing script gets reported as a failure, never as a saved preference.
With off, later events stop reaching the collector. Local logs keep being written and nothing already stored disappears. An opt-out from the environment outranks a saved on, and a maintainer-side hard disable outranks both, cutting collection and local logging too. The skill itself is left out of usage telemetry.
The choice applies per user and per plugin. Node.js is the one requirement: no PAC, no sign-in, no native build tools. Without Node.js on the machine the script cannot run, so whatever was set before stays in force.
What it helps with
- opt out of usage telemetry with a single
offargument - check the current setting without passing anything
- switch transmission back on after testing
- confirm local diagnostic logs survive the opt-out
- work out which wins between an environment opt-out and a saved
on
Example prompts for the agent
- Turn off telemetry for the Power Apps Mobile Extension skills.
- What's the telemetry status right now?
- Enable telemetry again, argument
on.
How to install telemetry
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install power-apps-mobile-extension@power-platform-skillsThis installs the whole power-apps-mobile-extension 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-apps-mobile-extension/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-apps-mobile-extension/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?
Use the marketplace: run /plugin marketplace add microsoft/power-platform-skills, then /plugin install power-apps-mobile-extension@power-platform-skills.
What does the telemetry skill do?
It turns usage telemetry for the Power Apps Mobile Extension skills on or off, or reports the current state. The setting is kept per user and per plugin.
Does off erase what was already collected?
No. It stops later events from being sent, while local logging carries on. An environment opt-out or a maintainer-side hard disable can override the choice.
Source text
SKILL.md · MIT
--- name: telemetry description: "Enable, disable, or check usage telemetry transmission for Power Apps Mobile Extension skills. Use for 'turn off telemetry', 'opt out', 'enable telemetry', or 'telemetry status'. Opt-out stops transmission only; local diagnostic logs continue when the plugin is enabled." user-invocable: true argument-hint: "on | off | status" allowed-tools: Read, Bash --- # Telemetry Transmission Preference 1. Read [shared-instructions.md](../../shared/shared-instructions.md). This control requires Node.js but does not require PAC, authentication or native build tools. 2. Read the action from the user's request: `on`, `off`, or `status`. Missing or invalid arguments mean `status`. 3. Run the local control, using the absolute installed plugin root provided by the host (`PLUGIN_ROOT` or `CLAUDE_PLUGIN_ROOT`): ```text node "<plugin-root>/scripts/telemetry-config.js" --action <on|off|status> ``` Resolve the root from the installed skill location if necessary, never from an arbitrary file in the control project. Do not run an install or sign-in command. 4. Show the command output verbatim. If it fails, report the failure instead of claiming the preference was saved. Do not modify the plugin's telemetry config. The choice is per-user and per-plugin. `off` stops collector transmission on subsequent events; it does not stop local logging or delete existing data. The environment opt-out overrides a saved `on` choice. The maintainer-controlled hard-disabled configuration overrides both and stops collection and local logging. This skill is excluded from usage telemetry. See [telemetry.md](../../shared/telemetry.md) for fields, locations, routing and the maintainer-controlled release switch.
© Microsoft · MIT · microsoft/power-platform-skills
Similar skills
All skills for Agent setup: memory, context, orchestration →telemetry by other authors comes first.