New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Instrumenting First Party Metrics

by PostHog in PostHog/posthog

How to instrument PostHog's own Metrics product from PostHog-owned code — record counters, gauges, and histograms that land in posthog.metrics, the same way customers do.

OfficialCustom licenceAuto-check passedDevelopment

Install Instrumenting First Party Metrics

skills CLI
$ npx skills add PostHog/posthog --skill instrumenting-first-party-metrics -a claude-code

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

GitHub CLI
$ gh skill install PostHog/posthog instrumenting-first-party-metrics --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/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/instrumenting-first-party-metrics .claude/skills/instrumenting-first-party-metrics && 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
instrumenting-first-party-metrics
GitHub stars
40k
Token cost
~2.2k tokens
SKILL.md length
866 words
Files
1
Skills in repo
254
Repo updated
First seen
Licence
Custom licence

At a glance

How to instrument PostHog's own Metrics product from PostHog-owned code — record counters, gauges, and histograms that land in posthog.metrics, the same way customers do.

  • Works in 4 steps: identify the environment and pick the path → check the version gate (don't assume) → instrument (keep it doc-shaped) → …
  • Adding application metrics in this monorepo (web
  • SKILL.md covers Step 1 — identify the…, Step 2 — check the version…, Step 3 — instrument (keep it… and Step 4 — validate it actually…, plus 2 more sections
  • Needs OTEL_METRICS_EXPORT_TOKEN

What it does

Instrumenting First Party Metrics is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to instrument PostHog's own Metrics product from PostHog-owned code — record counters, gauges, and histograms that land in posthog.metrics, the same way customers do. Use when adding application metrics in this monorepo (web, Celery, Temporal), when asked to push or ship metrics into posthog metrics, or when unsure whether the SDK in this environment supports posthog.metrics yet. Covers the environment decision (SDK-first per the public docs, OTel fallback when the SDK path is not available), the exact…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Monorepo tooling and Background jobs. It works with PostHog and OpenTelemetry. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…

When your agent uses it

  • Adding application metrics in this monorepo (web
  • Ship metrics into posthog metrics
  • Unsure whether the SDK in this environment supports posthog.metrics yet

Example prompts

  • “/instrumenting-first-party-metrics”

Requirements

  • Python 3
  • Node.js
  • A credential in OTEL_METRICS_EXPORT_TOKEN

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. identify the environment and pick the path
  2. check the version gate (don't assume)
  3. instrument (keep it doc-shaped)
  4. validate it actually works

What it can do on your machine

Read from SKILL.md and the folder at commit c012c8d. 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 (its code samples are python).

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

  • Network

    Links to these hosts (documentation or services it may open):

    • posthog.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OTEL_METRICS_EXPORT_TOKEN

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

Context cost

Instrumenting First Party Metrics loads about 2.2k tokens when it runs. Until then it costs about 162 tokens; SKILL.md has 866 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~162
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

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 866 words (~2,217 tokens).

“Goal: get application metrics from PostHog's own code into the PostHog Metrics product (posthog.metrics table, Metrics UI), the same way customers do. Follow the public docs wherever possible; use OTel only as the fallback when the SDK path isn't available…”

— opening of SKILL.md by PostHog, Custom licence
name
instrumenting-first-party-metrics

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/instrumenting-first-party-metrics of PostHog/posthog.

Open the folder on GitHubat commit c012c8d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Instrumenting First Party Metrics 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.

Instrumenting First Party Metrics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Instrumenting First Party Metrics this skillPostHog/posthog40k—~2.2kAutomated safety check: PassCustom licence
Adapter Alignmentevloghq/evlog1.9k—~1.3kAutomated safety check: PassMIT
Hk Local Logsdeepklarity/harness-kit100—~2.1kAutomated safety check: NotesMIT
Temps Best Practicesgotempsh/temps833—~2.9kAutomated safety check: PassApache-2.0
Sentry Python SDKgetsentry/sentry-for-ai268—~4.1kAutomated safety check: PassApache-2.0
Nx Importnrwl/nx29k6 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Adapter Alignment

    evloghq/evlog

    Twice-monthly check that evlog's drain adapters still send what each provider's own client sends.

    1.9k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Hk Local Logs

    deepklarity/harness-kit

    Inspect and debug errors via logs across the harness-kit monorepo.

    100 GitHub stars~2.1k tokensUpdated 2 mo ago
    DevelopmentAuto-check: notes

  • Temps Best Practices

    gotempsh/temps

    Best-practices reference for preparing and instrumenting applications on Temps.

    833 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Sentry Python SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Python. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~4.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Nx Import

    nrwl/nx

    Import, merge, or combine repositories into an Nx workspace using nx import.

    29k GitHub starsUsed in 6 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Nx Workspace

    nomcopter/react-mosaic

    Explore and understand Nx workspaces. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 8 repos~1.9k tokens
    DevelopmentAuto-check passed

More from PostHog/posthog

All 254 skills in this repo

  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Autoresolving PR Conflicts

    PostHog/posthog

    Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Diagnosing Stacktrace Symbolication

    PostHog/posthog

    Official

    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Instrumenting First Party Metrics

What does Instrumenting First Party Metrics do?

How to instrument PostHog's own Metrics product from PostHog-owned code — record counters, gauges, and histograms that land in posthog.metrics, the same way customers do. Instrumenting First Party Metrics is an agent skill from PostHog/posthog, published by the product's own GitHub organization.metrics, the same way customers do.

When should I use Instrumenting First Party Metrics?

Instrumenting First Party Metrics fits situations like: adding application metrics in this monorepo (web; ship metrics into posthog metrics; unsure whether the SDK in this environment supports posthog.metrics yet.

How do I install Instrumenting First Party Metrics in Claude Code?

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

How do I install Instrumenting First Party Metrics in Codex?

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

Can I use Instrumenting First Party Metrics 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 PostHog/posthog --skill instrumenting-first-party-metrics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/instrumenting-first-party-metrics, .gemini/skills/instrumenting-first-party-metrics, .github/skills/instrumenting-first-party-metrics and .opencode/skills/instrumenting-first-party-metrics in your project.

What does Instrumenting First Party Metrics need to run?

Going by SKILL.md and its folder, Instrumenting First Party Metrics needs credentials named OTEL_METRICS_EXPORT_TOKEN. Our summary lists: Python 3; Node.js; A credential in OTEL_METRICS_EXPORT_TOKEN.

Does Instrumenting First Party Metrics access the network?

SKILL.md names 1 domain. As links in the text: posthog.com. This is read from the text; nothing was executed.

Is Instrumenting First Party Metrics 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 Instrumenting First Party Metrics use?

Instrumenting First Party Metrics 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 Instrumenting First Party Metrics use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Instrumenting First Party Metrics?

Skills that share tags, products or a category with Instrumenting First Party Metrics: Adapter Alignment (evloghq/evlog, 1.9k stars), Hk Local Logs (deepklarity/harness-kit, 100 stars), Temps Best Practices (gotempsh/temps, 833 stars) and Sentry Python SDK (getsentry/sentry-for-ai, 268 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Instrumenting First Party Metrics?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 2026.

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