Logs Datadog

posthog/logs-datadog

PostHog logs for Datadog

10k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

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-datadog

39 160 bytes besides the instruction

references/best-practices.md

references/datadog.md

references/debug-logs-mcp.md

references/link-session-replay.md

references/search.md

references/start-here.md

references/troubleshooting.md

4 sections, as written by the author

This skill helps you add PostHog log ingestion to Datadog applications.

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

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.

_No specific framework guidelines._

Copy the folder

Take posthog/logs-datadog 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.