Blyp PostHog
Install blyp-posthog after blyp-core when Blyp logs or errors must flow into PostHog. This preset keeps agents on the official connector model, including mode: "auto" or mode: "manual" and Blyp-managed forwarding from browser or Expo clients.
When to install it
- the repo configures
connectors.posthog - logs should flow into PostHog Logs
- Blyp-managed errors should flow into PostHog Error Tracking
- browser or Expo code requests
connector: "posthog"
What it covers
connectors.posthog- auto vs manual mode
- error tracking configuration
- client and Expo forwarding through Blyp first
Download raw skill file
Use the canonical source file directly if you want to copy it into an agent skill directory without copying from the rendered page.
/skills/blyp-posthog/SKILL.md| Agent | Project-local path | Global path |
|---|---|---|
| Codex | .agents/skills/blyp-posthog/SKILL.md | ~/.agents/skills/blyp-posthog/SKILL.md |
| OpenCode | .opencode/skills/blyp-posthog/SKILL.md | ~/.config/opencode/skills/blyp-posthog/SKILL.md |
| Claude Code | .claude/skills/blyp-posthog/SKILL.md | ~/.claude/skills/blyp-posthog/SKILL.md |
Related docs
Canonical skill source
Copy the exact markdown file contents and drop them into your agent skill directory.
---
name: blyp-posthog
description: Portable Blyp connector add-on skill for PostHog using connectors.posthog, auto or manual delivery modes, and server-side error tracking that can receive browser or Expo forwarding requests through Blyp.
---
# Blyp PostHog
## What this skill is for
Use this add-on when Blyp logs or errors should be forwarded into PostHog.
## When to use it
- Configuring `connectors.posthog`
- Choosing `mode: "auto"` or `mode: "manual"`
- Enabling PostHog error tracking
- Supporting browser or Expo requests that ask Blyp to forward into PostHog
## Blyp-specific rules and constraints
- Install `blyp-core` first.
- Configure PostHog on the server in `connectors.posthog`.
- Supported delivery modes are `auto` and `manual`.
- Error tracking is configured under `connectors.posthog.errorTracking`.
- Browser and Expo PostHog requests still send to Blyp ingestion first.
- Client `error` and `critical` logs are promoted to PostHog exceptions only when server-side PostHog error tracking is enabled in `auto` mode.
## Required implementation steps
1. Add or update `connectors.posthog` in `blyp.config.*`.
2. Set `enabled: true` and choose `mode: "auto"` or `mode: "manual"`.
3. Provide `projectKey` and optional `host` or `serviceName`.
4. If the application wants Blyp-managed exception capture, configure `errorTracking`.
5. If manual control is required, use `@blyp/core/posthog` APIs instead of assuming auto delivery.
6. If browser or Expo code requests `connector: "posthog"`, verify the server connector is configured first.
## Verification checklist
- `connectors.posthog` exists in `blyp.config.*`
- The chosen mode is explicit: `auto` or `manual`
- Error tracking is configured intentionally when needed
- Browser or Expo PostHog forwarding still targets Blyp ingestion first
- Manual code imports from `@blyp/core/posthog` when auto mode is not desired
## References
- Config key: `connectors.posthog`
- Manual import path: `@blyp/core/posthog`
- Manual APIs: `createPosthogLogger()`, `createStructuredPosthogLogger()`, `createPosthogErrorTracker()`, `capturePosthogException()`