skillboardUpdated every 6 hours
skillboardGuides adding, changing, and reviewing telemetry through the `@n8n/telemetry` event registry. Use when working on telemetry, analytics, tracking, product events, `track()` calls, or RudderStack/PostHog product events, in frontend or backend code — and whenever you need to find which registered telemetry events exist, what an event means, or what properties it carries.
Telemetry The registry Events migrated to the registry live in as one entry per event — its exact emitted name, a description, and a zod schema typing its properties — organized per product domain in and composed into . The package defines registered events and never depends on transport SDKs. To find which events are registered, what they mean, or what properties they carry, run the catalog first: The registry is being adopted incrementally. Events not yet registered do not appear in the…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/telemetry · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/telemetry"
cp -r ".agents/skills/telemetry" ".claude/skills/telemetry"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.