workleap/wl-squide · Archived

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 tr…

First seen Feb 28, 2026

Installation

$ npx skills add workleap/wl-squide --skill workleap-telemetry

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from workleap/wl-squide · top by installs.

npx skills add workleap/wl-squide

Browse all from workleap/wl-squide

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 8
License LICENSE
Default branch main
Open issues 3
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version3.2
More metadata
version
3.2

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,237 B
  • docs SUMMARY.md 709 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

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

  1. Use umbrella package — Always use @workleap/telemetry, not standalone packages
  2. Do not invent APIs — Only use documented APIs from references
  3. Correlation is automatic — Never manually set Telemetry Id or Device Id; never create your own TelemetryContext instances
  4. Noop for non-production — Use NoopTelemetryClient in Storybook/tests
  5. Privacy matters — Never log PII to LogRocket; use data-public/data-private attributes
  6. productFamily is requiredinitializeTelemetry 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