Error Tracking Go

posthog/error-tracking-go

PostHog error tracking for Go

8k 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 error-tracking-go

29 875 bytes besides the instruction

references/alerts.md

references/assigning-issues.md

references/fingerprints.md

references/go.md

references/monitoring.md

references/upload-source-maps.md

4 sections, as written by the author

This skill helps you add PostHog error tracking to Go applications.

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

Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.
Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
Manual capture for boundaries: Use captureException() at error boundaries and catch blocks for errors that don't propagate to the global handler.

_No specific framework guidelines._

Copy the folder

Take posthog/error-tracking-go 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.