Skip to content

microsoft/power-platform-skills / plugins/model-apps/skills/telemetry

telemetry

Verified

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".

FileKindSize
SKILL.mdskill md761 B
telemetry-workflow.mdmarkdown3.4 KB

telemetry-workflow.md

View on GitHub
# Telemetry control workflow

The user invoked `/<plugin>:telemetry [on | off | status]` to control usage
telemetry for this plugin. Default to `status` when no argument is given.

## Steps

1. Read the action from `$ARGUMENTS`. It must be one of `on`, `off`, or `status`.
   If it is empty or anything else, use `status`.
2. For Power Pages, run its plugin-specific CLI:

   ```bash
   node "${PLUGIN_ROOT}/scripts/telemetry-config.js" --action <action>
   ```

   For other plugins, run the synced CLI (it auto-detects the plugin from the plugin manifest):

   ```bash
   node "${PLUGIN_ROOT}/scripts/lib/telemetry/lib/telemetry-config.js" --action <action>
   ```

3. Show the command's stdout to the user verbatim. Do not add or remove lines.

## What to know (for answering follow-ups)

- `off` stops transmission to Microsoft. **Nothing leaves the machine.**
- `on` re-enables transmission. The choice is **per-user and per-plugin** and
  takes effect on the next event (no restart).
- Events include skill name, plugin/PAC/agent versions, OS/Node versions, session
  and correlation IDs, and Dataverse organization and Entra tenant GUIDs when PAC
  is signed in.
  Power Pages can also include the signed-in user's Entra object ID as
  `eventInfo.aadObjectId` when PAC exposes it, and the SPA framework of the
  Power Pages code site being worked in (`react`, `vue`, `angular`, or `astro`)
  as `eventInfo.framework`. The framework name describes the scaffold only —
  it is never a site name or path. Model Apps excludes both.
  When plugin telemetry is enabled, the local diagnostic mirror retains the same
  event fields even when transmission is off.
  A plugin whose committed telemetry config has `disabled: true` writes no mirror.
- Power Pages non-SPA creation records `template_used` and
  `non_spa_creation_success`/`non_spa_creation_failure` using one creation
  `correlationId`, public catalog `eventInfo.templateId`, `eventInfo.templateKind`
  (`non-spa`), optional already-known `eventInfo.audience` (`internal`/`external`),
  and a fixed failure category. Success is a validated, committed downloaded baseline,
  before optional customization. Private correlation receipts under the config
  directory's `telemetry/power-pages/non-spa-creations/` retain selected catalog
  revision/common context and outcome markers even when transmission is off.
  Old receipts are pruned best-effort after 14 days on a later selection; hard-off
  writes none. No additional question, catalog fetch, or per-poll event is needed.
- Model Apps app builds (`--apply`) and page uploads record `skill_completed`
  when they finish: the outcome, duration, a fixed error class and per-phase
  step counts (or whether a page was created, updated or unchanged), with the
  organization and tenant GUIDs of the environment they targeted. App, table,
  page and environment names are never included.
- Events do not include file paths, prompts, tool inputs, site names, Dataverse
  URLs, credentials, usernames, or hostnames.
- **Automation/CI** can disable telemetry by setting the opt-out env var
  `POWER_PLATFORM_SKILLS_TELEMETRY_<PLUGIN>_OPTOUT=1` instead of running this
  command. The value can be `1` or `true` (the dotnet `*_TELEMETRY_OPTOUT`
  convention).
  `<PLUGIN>` is the plugin name uppercased with non-alphanumerics collapsed to `_`.
  This opt-out has the highest precedence — it overrides a saved choice from this
  command and even `on`. It suppresses transmission only, like `off`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall