pruff-skills 1.13.1 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +5 -6
  2. package/dist/cli.mjs +403 -588
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -257,12 +257,11 @@ see one, the message names the file, both versions, and what to run.
257
257
  **The CLI sends nothing.** pruff-skills ships with the upstream usage telemetry removed — running
258
258
  `add`, `update`, `find` or any other command emits no events.
259
259
 
260
- Separately, `pruff-skills analytics` can turn on **Claude Code's own** OpenTelemetry exporter and
261
- point it at Pruff's analytics backend, so an organisation can see which skills and tools its token
262
- spend goes to. It is opt-in and Pruff-internal: `analytics enable` is the only command that writes
263
- anything (never `add`, `update` or `onboarding`), the endpoint credentials live in the private
264
- catalog repo rather than in this package, and it exports no prompts, responses or file contents.
265
- `analytics status` shows what is on; `analytics disable` removes it.
260
+ Versions 0.11.0 to 1.14.0 had `pruff-skills analytics enable`, which pointed **Claude Code's own**
261
+ OpenTelemetry exporter at Pruff's PostHog project by writing an `env` block into
262
+ `~/.claude/settings.json`. It was retired in 2.0.0. `update` now removes that block whenever it finds
263
+ it (only when it points at Pruff's PostHog, so your own OpenTelemetry setup is left alone), and
264
+ `analytics disable` removes it on demand. `analytics status` shows whether it is still there.
266
265
 
267
266
  ## Attribution
268
267