← LeaderboardThe Skill Leaderboard

telemetry

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.

Published by microsoft ↗microsoft/power-platform-skills

Try your first task

Check Mobile Extension telemetry transmission

Start a fresh conversation.

Use the Power Apps Mobile Extension telemetry skill to report the current transmission preference. Read its shared instructions, resolve the absolute installed plugin root from the host or skill location, and run the local telemetry-config.js status action with Node.js. Show the output verbatim and report failures honestly. Explain that opting out of transmission would still leave local diagnostic logs when the plugin is enabled. Do not install, sign in, require PAC/native tools, edit telemetry configuration directly or change the setting in this status task.

    User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

    SKILL.md

    name: telemetrydescription: "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: trueargument-hint: "on | off | status"allowed-tools: Read, Bash

    Telemetry Transmission Preference

    1. Read 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):

      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 for fields, locations, routing and the maintainer-controlled release switch.