How do I install the Workleap Telemetry skill?

Run npx skillmds@latest add workleap/workleap-telemetry-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workleap Telemetry safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workleap Telemetry?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workleap Telemetry free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workleap Telemetry?

workleap (@workleap) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workleap Telemetry by workleap — Agent Skill

Name: Workleap Telemetry
Author: workleap

Workleap Telemetry

Guide for @workleap/telemetry, Workleap's unified telemetry connecting Honeycomb, LogRocket, and Mixpanel with automatic correlation IDs. Use this skill when: (1) Initializing wl-telemetry in a frontend application (2) Correlation values (Telemetry Id, Device Id) and cross-tool data correlation (3) Honeycomb tracing, OpenTelemetry spans, and performance monitoring (4) LogRocket session replay, user identification, and privacy controls (5) Mixpanel analytics, event tracking, and cross-product tracking (6) Configuring wl-telemetry diagnostic loggers (LogRocketLogger) (7) Storybook/test setup with Noop telemetry clients (8) Reviewing or troubleshooting telemetry instrumentation

workleap Updated Sep 21, 2026

File contents

Workleap Telemetry (wl-telemetry)

@workleap/telemetry is an umbrella package that integrates Honeycomb, LogRocket, and Mixpanel with consistent correlation IDs for unified debugging and analysis.

Critical Rules

Use umbrella package — Always use @workleap/telemetry, not standalone packages
Do not invent APIs — Only use documented APIs from references
Correlation is automatic — Never manually set Telemetry Id or Device Id; never create your own TelemetryContext instances
Noop for non-production — Use NoopTelemetryClient in Storybook/tests
Privacy matters — Never log PII to LogRocket; use data-public/data-private attributes
productFamily is required — initializeTelemetry requires "wlp" or "sg" as the first argument

Reference Guide

For detailed documentation beyond the rules above, consult:

references/api.md — Initialization options, TelemetryClient properties, Honeycomb/LogRocket/Mixpanel client APIs, React hooks, Noop clients, LogRocketLogger
references/integrations.md — Platform-specific configuration, Honeycomb tracing patterns, LogRocket privacy and user identification, Mixpanel event tracking, cross-platform correlation workflows
references/examples.md — Full application setup, Storybook/test configuration, user identification, custom Honeycomb traces, Mixpanel tracking patterns, logging configuration, troubleshooting

---name: workleap-telemetry-2description: Guide for @workleap/telemetry, Workleap's unified telemetry connecting Honeycomb, LogRocket, and Mixpanel with automatic correlation IDs. Use this skill when: (1) Initializing wl-telemetry in a frontend application (2) Correlation values (Telemetry Id, Device Id) and cross-tool data correlation (3) Honeycomb tracing, OpenTelemetry spans, and performance monitoring (4) LogRocket session replay, user identification, and privacy controls (5) Mixpanel analytics, event tracking, and cross-product tracking (6) Configuring wl-telemetry diagnostic loggers (LogRocketLogger) (7) Storybook/test setup with Noop telemetry clients (8) Reviewing or troubleshooting telemetry instrumentation---# Workleap Telemetry (wl-telemetry)`@workleap/telemetry` is an umbrella package that integrates Honeycomb, LogRocket, and Mixpanel with consistent correlation IDs for unified debugging and analysis.## Critical Rules1. **Use umbrella package** — Always use `@workleap/telemetry`, not standalone packages2. **Do not invent APIs** — Only use documented APIs from references3. **Correlation is automatic** — Never manually set Telemetry Id or Device Id; never create your own `TelemetryContext` instances4. **Noop for non-production** — Use `NoopTelemetryClient` in Storybook/tests5. **Privacy matters** — Never log PII to LogRocket; use `data-public`/`data-private` attributes6. **productFamily is required** — `initializeTelemetry` requires `"wlp"` or `"sg"` as the first argument## Reference GuideFor detailed documentation beyond the rules above, consult:- **`references/api.md`** — Initialization options, TelemetryClient properties, Honeycomb/LogRocket/Mixpanel client APIs, React hooks, Noop clients, LogRocketLogger- **`references/integrations.md`** — Platform-specific configuration, Honeycomb tracing patterns, LogRocket privacy and user identification, Mixpanel event tracking, cross-platform correlation workflows- **`references/examples.md`** — Full application setup, Storybook/test configuration, user identification, custom Honeycomb traces, Mixpanel tracking patterns, logging configuration, troubleshooting

Frequently asked questions