Agent skill

Posthog Instrumentation

by langfuse in langfuse/langfuse

Product analytics with posthog. An agent skill from langfuse/langfuse.

Custom licenceAuto-check passedData & Analytics

Install Posthog Instrumentation

skills CLI
$ npx skills add langfuse/langfuse --skill posthog-instrumentation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install langfuse/langfuse posthog-instrumentation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/posthog-instrumentation .claude/skills/posthog-instrumentation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
posthog-instrumentation
GitHub stars
36k
Token cost
~3.2k tokens
SKILL.md length
1,624 words
Files
3 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
Custom licence

At a glance

Product analytics with posthog. An agent skill from langfuse/langfuse.

  • Works in 6 steps: PRIVACY is rule #1 — metadata only,… → Instrument the INTENT seam, not the… → Fire once per action — dedup. Guard… → …
  • Adding a meaningful user action
  • SKILL.md covers Propose instrumentation when…, The Langfuse pattern (match it…, The 6 rules (each earned the… and Session replay privacy, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Posthog Instrumentation is an agent skill from langfuse/langfuse. Product analytics with posthog. Use when adding a meaningful user action or feature in web/, touching PostHog capture code, changing session replay or its privacy boundaries, or answering product-usage questions.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/posthog-best-practices.md` and `references/posthog-code-patterns.md`).

It sits in Data & Analytics, covering Product analytics and Observability. It works with PostHog and Langfuse. The repository describes itself as: 🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.

When your agent uses it

  • Adding a meaningful user action
  • Feature in web/
  • Touching PostHog capture code
  • Changing session replay

Example prompts

  • “/posthog-instrumentation”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. PRIVACY is rule #1 — metadata only, never raw values. Safe: type,
  2. Instrument the INTENT seam, not the low-level setter. Capture in the
  3. Fire once per action — dedup. Guard no-op triggers (a blur with no
  4. **Carry the key segmentation DIMENSION on every event — and make sure it is
  5. Cover every sub-path of a surface. A "filter applied" event that only
  6. VERIFY LIVE — intercept the real capture calls; do not assume. Spy on

What it can do on your machine

Read from SKILL.md and the folder at commit 389f393. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Posthog Instrumentation loads about 3.2k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 1,624 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,624 words (~3,225 tokens).

“One idea: every event exists to answer a question ("how do people filter?", "v3 vs v4?"), and it captures shape/metadata — NEVER raw values. If you cannot name the question an event answers, do not add it. If a property…”

— opening of SKILL.md by langfuse, Custom licence
name
posthog-instrumentation

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in .agents/skills/posthog-instrumentation of langfuse/langfuse.

  • SKILL.md
  • references/posthog-best-practices.md
  • references/posthog-code-patterns.md

Open the folder on GitHubat commit 389f393

Compare with similar skills

Posthog Instrumentation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Posthog Instrumentation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Posthog Instrumentation this skilllangfuse/langfuse36k—~3.2kAutomated safety check: PassCustom licence
Telemetry Standardssupabase/supabase111k—~2kAutomated safety check: PassApache-2.0
Prod TelemetryUsefulSoftwareCo/executor4.1k—~1.9kAutomated safety check: PassMIT
Posthog Product Health Auditboardsesh/boardsesh164—~2.1kAutomated safety check: PassApache-2.0
Creating Box Plot InsightsPostHog/posthog40k—~1.1kAutomated safety check: PassCustom licence
Querying Posthog DataPostHog/posthog40k—~4.2kAutomated safety check: PassCustom licence

Similar skills

  • Telemetry Standards

    supabase/supabase

    Official

    PostHog event tracking standards for Supabase Studio. An agent skill from supabase/supabase.

    111k GitHub stars~2k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Prod Telemetry

    UsefulSoftwareCo/executor

    Query Executor's production telemetry — Axiom traces (executor-cloud dataset), prod Postgres via PlanetScale, PostHog product analytics — through the Executor MCP.

    4.1k GitHub stars~1.9k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Posthog Product Health Audit

    boardsesh/boardsesh

    Mine Boardsesh's PostHog telemetry (error tracking, session recordings, product analytics) with a multi-agent workflow, then file verified, deduplicated, severity-labelled GitHub issues.

    164 GitHub stars~2.1k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Official

    Creates product analytics or SQL-backed box plot insights in PostHog.

    40k GitHub stars~1.1k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Querying Posthog Data

    PostHog/posthog

    Official

    Explains how to query PostHog data, defaulting to typed runners for supported product analytics.

    40k GitHub stars~4.2k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Posthog Analytics

    alinaqi/maggy

    PostHog analytics, event tracking, feature flags, dashboards

    707 GitHub starsUsed in 1 repo~5.2k tokens
    Data & AnalyticsAuto-check: notes

More from langfuse/langfuse

All 33 skills in this repo
  • Linear Context Handover

    langfuse/langfuse

    Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it.

    36k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Add Model Price

    langfuse/langfuse

    A skill your agent uses when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI…

    36k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Backend Dev Guidelines

    langfuse/langfuse

    Build or review Langfuse backend code. An agent skill from langfuse/langfuse.

    36k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Navigate Langfuse repositories, code areas, and agent skills.

    36k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Refactor React Effects

    langfuse/langfuse

    Refactor avoidable React useEffect usage in Langfuse frontend code.

    36k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Add To Dependabot CSV

    langfuse/langfuse

    Append GitHub Dependabot or Snyk/code-scanning alerts to an existing vulnerability CSV after verifying their API metadata.

    36k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Works with

Questions about Posthog Instrumentation

What does Posthog Instrumentation do?

Product analytics with posthog. An agent skill from langfuse/langfuse. Posthog Instrumentation is an agent skill from langfuse/langfuse. Product analytics with posthog.

When should I use Posthog Instrumentation?

Posthog Instrumentation fits situations like: adding a meaningful user action; feature in web/; touching PostHog capture code; changing session replay.

How do I install Posthog Instrumentation in Claude Code?

Run `npx skills add langfuse/langfuse --skill posthog-instrumentation -a claude-code`. Or copy the skill folder (.agents/skills/posthog-instrumentation in langfuse/langfuse) into .claude/skills/posthog-instrumentation in your project. Claude Code loads it when a task matches its description.

How do I install Posthog Instrumentation in Codex?

Run `npx skills add langfuse/langfuse --skill posthog-instrumentation -a codex`. Or copy the skill folder (.agents/skills/posthog-instrumentation in langfuse/langfuse) into .agents/skills/posthog-instrumentation in your project. Codex loads it when a task matches its description.

Can I use Posthog Instrumentation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langfuse/langfuse --skill posthog-instrumentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/posthog-instrumentation, .gemini/skills/posthog-instrumentation, .github/skills/posthog-instrumentation and .opencode/skills/posthog-instrumentation in your project.

What does Posthog Instrumentation need to run?

SKILL.md names no scripts, command-line tools or credentials: Posthog Instrumentation is instructions for the agent only.

Does Posthog Instrumentation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Posthog Instrumentation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Posthog Instrumentation use?

Posthog Instrumentation has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Posthog Instrumentation use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.

What are the alternatives to Posthog Instrumentation?

Skills that share tags, products or a category with Posthog Instrumentation: Telemetry Standards (supabase/supabase, 111k stars), Prod Telemetry (UsefulSoftwareCo/executor, 4.1k stars), Posthog Product Health Audit (boardsesh/boardsesh, 164 stars) and Creating Box Plot Insights (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Posthog Instrumentation?

langfuse (a GitHub organization) maintains it in langfuse/langfuse, which has 35,555 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.

Source: langfuse/langfuse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.