fix: Include currentAgentSkillsInstalled in command telemetry events

[dario-piotrowicz]

Fixes #[insert GH or internal issue link(s)].

Describe your change...

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: already documented in telemetry.md

A picture of a cute animal (not mandatory, but encouraged)

[changeset-bot]

🦋 Changeset detected

Latest commit: 645faf3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
wrangler	Patch
@cloudflare/vite-plugin	Patch
@cloudflare/vitest-pool-workers	Patch
@cloudflare/wrangler-bundler	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ask-bonk]

The doc claim holds — telemetry.md line 30 covers this.

Now let me assess the core logic once more for a real bug. The critical question: does wrapping command dispatch in the async telemetryCurrentAgentSkillsInstalled() chain risk the "started" event being sent AFTER "completed"?

Both events capture amplitude_event_id synchronously (0 for started, 1 for completed). The actual network dispatch ordering doesn't matter for analytics since ordering is reconstructed from amplitude_event_id. The memoized promise resolves once; both .then callbacks fire in registration order (started registered first). So even network ordering is preserved. No bug.

Let me double-check the agent detection failure path and that the inner .catch doesn't swallow something it shouldn't. The structure is sound: telemetryCurrentAgentSkillsInstalled().catch(() => null) ensures the value defaults to null, then dispatch, then a final .catch logs dispatch errors. This mirrors the adhoc event exactly.

The PR is a faithful, minimal fix that mirrors the existing adhoc-event pattern, is properly tested (the reused object includes the new property, covering started/completed/errored), preserves event-ordering semantics, handles errors correctly, and the documentation claim is accurate.

I've verified:

• No logic bug in the async wrapping (event IDs captured synchronously; ordering preserved)
• Error handling is equivalent/correct
• Test coverage includes the new property across started/completed/errored events
• Doc claim in telemetry.md is accurate
• Type safety is unaffected (uses existing loose Properties record pattern, consistent with adhoc events)

LGTM

github run

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@14155

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@14155

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@14155

miniflare

npm i https://pkg.pr.new/miniflare@14155

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@14155

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@14155

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@14155

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@14155

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@14155

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@14155

wrangler

npm i https://pkg.pr.new/wrangler@14155

@cloudflare/wrangler-bundler

npm i https://pkg.pr.new/@cloudflare/wrangler-bundler@14155

commit: 645faf3

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[workers-devprod]

Codeowners reviews satisfied

[github-actions]

⚠️ Issues found

.changeset/include-agent-skills-in-command-events.md

• Version Type: This changeset is categorized as patch, but it describes a telemetry/analytics change (including agent skill installation status in all telemetry events). Per the review criteria and changeset guidelines: "If the change collects more analytics, it should be a minor even though there is no user-visible change." This should be bumped to minor.