logs-go

Name: logs-go
Author: posthog

github.com/posthogCloud & DevOps7690 installsUpdated today

About logs-go

A skill for developers adding PostHog log ingestion to Go applications. It covers configuring an OTLP exporter through OpenTelemetry and recommends structured logs while preserving existing logging code.

Key features

01Configure OpenTelemetry log export
02Use an OTLP exporter
03Structured logging guidance
04Set keys and endpoints with environment variables
05References for log search and troubleshooting

Use cases

01Send Go application logs to PostHog
02Add log export alongside an existing logging system
03Troubleshoot log ingestion

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/skills --skill logs-go

After installing, type/logs-goin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

best-practices.md

debug-logs-mcp.md

go.md

link-session-replay.md

search.md

start-here.md

troubleshooting.md

Details

From the project README

PostHog logs for Go

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

Reference files

references/go.md - Go 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

Markdown supported

Details

Author: posthog
Repository: posthog/skills
Category: Cloud & DevOps
Installs: 90
GitHub stars: 76

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.