mcpbeat

Logs Nodejs

posthog/skills-logs-nodejs

PostHog logs for Node.js

This is a copy. The original lives at posthog/logs-nodejs.

10k tokens
context cost
the whole folder, loaded on every use
8
files
instructions only
0
copies elsewhere
how many repositories repackaged it
57
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/PostHog/skills --skill logs-nodejs

What comes with it

39 753 bytes besides the instruction
references/best-practices.md
references/debug-logs-mcp.md
references/link-session-replay.md
references/nodejs.md
references/search.md
references/start-here.md
references/troubleshooting.md

The instruction itself

4 sections, as written by the author

PostHog logs for Node.js

This skill helps you add PostHog log ingestion to Node.js applications.

Reference files

  • references/nodejs.md - Node.js logs installation - docs
  • references/start-here.md - Getting started with logs - docs
  • references/search.md - Search logs - docs
  • references/best-practices.md - Logging best practices - docs
  • references/troubleshooting.md - Logs troubleshooting - docs
  • references/link-session-replay.md - Link session replay - docs
  • references/debug-logs-mcp.md - Debug logs with mcp - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.
  • Minimal changes: Add log export alongside existing logging. Don't replace or restructure existing logging code.
  • OpenTelemetry: PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.
  • Structured logging: Prefer structured log formats with key-value properties over plain text messages.

Framework guidelines

_No specific framework guidelines._

How to use it

Copy the folder

Take posthog/skills-logs-nodejs from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.