In brief
PostHog Newspapers for Java
What it does
- Reference files
- Basic principles
- Framework directives
Who it is for, and an example
People whose task corresponds: PostHog logs for Java
Example request: "PostHog Newspapers for Java: PostHog Newspapers for Java"
PostHog Newspapers for Java Example written by iadujour.fr from the SKILL.md, not tested.
Install
Claude Code : /plugin marketplace add PostHog/skills, puis /plugin install posthog-all@posthog-skills (README).
/plugin marketplace add PostHog/skills/plugin install posthog-all@posthog-skillsWorks with
- Claude Code
Source: K0: marketplace K1: K2: Other agents are not appointed.
Level: Intermediate
Supposes a project already in place at the publisher and the tools described in the K0.
Good to know
SKILL.md excerpt
The original description, which the agent reads to decide whether to load the skill (in English):
PostHog logs for Java
Quoted from SKILL.md at commit 445764b . The folder also contains 7 extra files (references/).
The SKILL.md has 35 lines and 3 main sections:
- Reference files
- Key principles
- Framework guidelines
Licence: MIT
Checked on 13 November 2026 : fichier de licence du dépôt.
The licence allows reuse: the full SKILL.md text is reproduced below, unmodified, with its licence notice.
Full SKILL.md text
Reproduced unmodified from PostHog/skills (commit 445764b) , © PostHog, under licence MIT (original licence file ).
Show the original SKILL.md (35 lines, in English)
---
name: logs-java
description: PostHog logs for Java
metadata:
author: PostHog
version: 1.9.4
---
# PostHog logs for Java
This skill helps you add PostHog log ingestion to Java applications.
## Reference files
- `references/java.md` - Java 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._
Comments.
A field note, a question, a precision on this skill? Comments are reviewed before publication.
Published comments
Loading comments…
Leave a comment
Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.