mcpbeat

Feature Flags Go

posthog/skills-feature-flags-go

PostHog feature flags for Go applications

This is a copy. The original lives at posthog/feature-flags-go.

32k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
57
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 feature-flags-go

What comes with it

124 832 bytes besides the instruction
references/adding-feature-flag-code.md
references/best-practices.md
references/go.md

The instruction itself

5 sections, as written by the author

PostHog feature flags for Go

This skill helps you add PostHog feature flags to Go applications.

Reference files

  • references/go.md - Go feature flags installation - docs
  • references/adding-feature-flag-code.md - Adding feature flag code - docs
  • references/best-practices.md - Feature flag best practices - docs

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

Key principles

  • Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
  • Minimal changes: Add feature flag code alongside existing logic. Don't replace or restructure existing code.
  • Boolean flags first: Default to boolean flag checks unless the user specifically asks for multivariate flags.
  • Server-side when possible: Prefer server-side flag evaluation to avoid UI flicker.

PostHog MCP tools

Check if a PostHog MCP server is connected. If available, look for tools related to feature flag management (creating, listing, updating, deleting flags). Use these tools to manage flags directly in PostHog rather than requiring the user to do it manually in the dashboard.

Framework guidelines

_No specific framework guidelines._

How to use it

Copy the folder

Take posthog/skills-feature-flags-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.