How do I install the Ekx Posthog skill?

Run npx skillmds@latest add ekinoxis-evm/ekx-posthog 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 Ekx Posthog safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ekx Posthog?

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 Ekx Posthog free to use?

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

Who published Ekx Posthog?

Ekinoxis-evm (@ekinoxis-evm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ekx Posthog by ekinoxis-evm — Agent Skill

Name: Ekx Posthog
Rating: 4.5 (4 reviews)
Author: Ekinoxis-evm

Ekx Posthog

Product analytics with PostHog — client and server capture, identifying users, feature flags, and what not to send. Use when adding event tracking, wiring a feature flag, or reviewing whether analytics is capturing something it should not.

Ekinoxis-evm Updated Sep 22, 2026

File contents

PostHog

Our product analytics (posthog-js + posthog-node).

Environment

VITE_POSTHOG_KEY=       # project API key — public by design
VITE_POSTHOG_HOST=      # https://us.i.posthog.com

The project key is meant to be public — it can only write events. It is not a secret, but it is a spam vector, so keep the ingestion endpoint behind a reverse proxy if event volume ever becomes a cost problem.

Client

posthog.init(import.meta.env.VITE_POSTHOG_KEY, {
  api_host: import.meta.env.VITE_POSTHOG_HOST,
  person_profiles: "identified_only",     // don't bill for anonymous profiles
  capture_pageview: true,
});

Server

import { PostHog } from "posthog-node";
const posthog = new PostHog(key, { host });

posthog.capture({ distinctId: userId, event: "loan_requested", properties: { amount_usdc: 5000 } });
await posthog.shutdown();     // serverless: REQUIRED, or events are lost

await posthog.shutdown() before a serverless function returns. posthog-node batches, and the function freezes with the batch unsent otherwise. This is the single most common reason server events "don't appear".

Identifying

posthog.identify(userId, { email: user.email });   // on login
posthog.reset();                                    // on logout — or the next user inherits the session

Use a stable internal id as distinctId. Not a wallet address (users have several, and they rotate), not an email (it changes).

What not to capture

In a portfolio that touches lending, real-estate purchases and payments, this matters more than the tracking itself:

❌ Private keys, seed phrases, session tokens, API keys — obviously
❌ Full wallet addresses as properties. They are a permanent pseudonymous identifier that links a person to their entire onchain history. Hash them, or capture only that a wallet exists.
❌ Identity documents, KYC fields, credit-score inputs
❌ Exact loan amounts tied to an identifiable individual — bucket them
✅ Event names, funnel steps, bucketed values, feature-flag exposure

Enable session recording only with masking on, and never on a KYC or payment form.

Feature flags

if (await posthog.isFeatureEnabled("new-auction-ui", userId)) { … }

Server-side flag checks are a network call — cache per request, and always have a default for when PostHog is unreachable. A flag service outage must not take the product down.

Gotchas

Missing shutdown() in serverless → lost events.
No reset() on logout → merged user identities, permanently.
Wallet addresses as properties → de-anonymisation.
person_profiles: "always" bills for every anonymous visitor.
Flag check with no fallback couples your uptime to theirs.

---name: ekx-posthogdescription: Product analytics with PostHog — client and server capture, identifying users, feature flags, and what not to send. Use when adding event tracking, wiring a feature flag, or reviewing whether analytics is capturing something it should not.---# PostHogOur product analytics (`posthog-js` + `posthog-node`).---## Environment```bashVITE_POSTHOG_KEY= # project API key — public by designVITE_POSTHOG_HOST= # https://us.i.posthog.com```The project key is meant to be public — it can only write events. It is not a secret,but it *is* a spam vector, so keep the ingestion endpoint behind a reverse proxy ifevent volume ever becomes a cost problem.---## Client```tsposthog.init(import.meta.env.VITE_POSTHOG_KEY, { api_host: import.meta.env.VITE_POSTHOG_HOST, person_profiles: "identified_only", // don't bill for anonymous profiles capture_pageview: true,});```## Server```tsimport { PostHog } from "posthog-node";const posthog = new PostHog(key, { host });posthog.capture({ distinctId: userId, event: "loan_requested", properties: { amount_usdc: 5000 } });await posthog.shutdown(); // serverless: REQUIRED, or events are lost```**`await posthog.shutdown()` before a serverless function returns.** `posthog-node`batches, and the function freezes with the batch unsent otherwise. This is the singlemost common reason server events "don't appear".---## Identifying```tsposthog.identify(userId, { email: user.email }); // on loginposthog.reset(); // on logout — or the next user inherits the session```Use a **stable internal id** as `distinctId`. Not a wallet address (users haveseveral, and they rotate), not an email (it changes).---## What not to captureIn a portfolio that touches lending, real-estate purchases and payments, this mattersmore than the tracking itself:- ❌ Private keys, seed phrases, session tokens, API keys — obviously- ❌ Full wallet addresses as properties. They are a permanent pseudonymous identifier that links a person to their entire onchain history. Hash them, or capture only that a wallet exists.- ❌ Identity documents, KYC fields, credit-score inputs- ❌ Exact loan amounts tied to an identifiable individual — bucket them- ✅ Event names, funnel steps, bucketed values, feature-flag exposureEnable session recording only with masking on, and never on a KYC or payment form.---## Feature flags```tsif (await posthog.isFeatureEnabled("new-auction-ui", userId)) { … }```Server-side flag checks are a network call — cache per request, and always have adefault for when PostHog is unreachable. A flag service outage must not take theproduct down.---## Gotchas1. **Missing `shutdown()`** in serverless → lost events.2. **No `reset()` on logout** → merged user identities, permanently.3. **Wallet addresses as properties** → de-anonymisation.4. **`person_profiles: "always"`** bills for every anonymous visitor.5. **Flag check with no fallback** couples your uptime to theirs.

Frequently asked questions