OpenHands telemetry-analytics
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts, use-tracking.ts, cloud funnel analytics, or analytics environment variables.
install
source · Clone the upstream repo
git clone https://github.com/OpenHands/OpenHands
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/OpenHands/OpenHands "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.agents/skills/telemetry-analytics" ~/.claude/skills/all-hands-ai-openhands-telemetry-analytics && rm -rf "$T"
manifest:
.agents/skills/telemetry-analytics/SKILL.mdsource content
Telemetry and Analytics
Preserve Canvas's single-client telemetry architecture, consent ownership, identity lifecycle, and canonical event contracts.
Workflow
- Read
before changing telemetry, analytics consent, PostHog configuration, Cloud funnel observability, or onboarding event capture.references/guide.md - Identify the single canonical owner and capture point for the behavior.
- Extend typed event functions and controlled property unions rather than calling the SDK directly.
- Verify consent, identity, backend transitions, and duplicate-capture behavior relevant to the change.
- Keep secrets, conversation content, raw hosts, and unbounded user data out of telemetry.
Reference
— Telemetry architecture, consent and identity invariants, event creation workflow, Cloud funnel headers, onboarding event dictionary, and analytics environment variables.references/guide.md