Skip to content

microsoft/power-platform-skills / plugins/pcf/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 pcf 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 md714 B
telemetry-workflow.mdmarkdown2.0 KB

telemetry-workflow.md

View on GitHub
# PCF telemetry control

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

## Steps

1. Read the action from `$ARGUMENTS`. Use `on`, `off` or `status`; if empty or
   unrecognized, use `status`.
2. Run the PCF control CLI:

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

3. Show stdout verbatim. If the command fails, show its error rather than
   claiming the preference was saved.

## What to know

- Usage telemetry is **enabled and default-on**, with no first-run prompt.
  PCF shares model-apps' 1DS tenant and keys.
- `status` reports the actual build state, effective transmission preference
  and local mirror location without changing settings.
- `on` and `off` save a per-user, per-plugin transmission preference as
  `telemetry["pcf"]` in `~/.power-platform-skills/config.json`. Other settings
  are preserved. The preference takes effect on the next event.
- `POWER_PLATFORM_SKILLS_TELEMETRY_PCF_OPTOUT=1` (or `true`) takes precedence
  over the saved preference and `on`. It disables transmission only.
- `skill_started` sends base fields: skill,
  plugin/PAC/agent versions, OS/Node versions, session/correlation IDs, and
  `orgId`/`tenantId` when PAC is signed in. There is **no user object ID**.
- When a control push finishes, `skill_completed` also records its outcome,
  duration, a fixed error class, whether the push was incremental and whether
  the registration was verified, with the `orgId`/`tenantId` of the environment
  it targeted. Control, solution and environment names are never sent.
- File paths, cwd, environment variables, prompts, arguments, tool inputs, site
  names, Dataverse URLs, stack traces, error messages, credentials, usernames
  and hostnames are never sent.
- The local diagnostic mirror at
  `~/.power-platform-skills/telemetry/pcf/sessions/<sessionId>/events.jsonl`
  retains the same approved fields even after a transmission opt-out.
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