posthog/ai-plugin

context-layer-consolidation

Keep the context wiki coherent using the deterministic lint report queue

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/posthog/ai-plugin --skill context-layer-consolidation

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Context layer consolidation

Start with scripts/lint --report. Work the queue on the current dream branch.

Only edit sourced Markdown content under org/, areas/, decisions/, and existing Space pages. Never edit repository instructions, generated indexes, or scripts/; report structural failures in the run summary for the server to repair.

  • Remove unsupported synthesis.
  • Remove expired priorities unless historically significant; mark those status: historical.
  • Mark replaced decisions superseded and link their replacement.
  • Merge near-duplicates and leave a wikilink from the old subject.
  • Resolve disagreements only with evidence; leave the rest explicit.
  • Repair or intentionally retain ghost links, add sources, and split oversized pages.
  • Name every deletion in the commit message.

Keep this bounded and evidence-led. Run scripts/lint after editing.

Related by task

from this repository

More skills

All skills
posthog
Official

exploring-llm-costs

Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.

1h installs
2
GitHub stars
98
Updated
Nov 6
posthog
Official

exploring-llm-traces

Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/ or /ai-observability/sessions/ ), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against events.properties.$aiinput / $aioutputchoices returns empty — message

1h installs
2
GitHub stars
98
Updated
Nov 6
posthog
Official

instrument-integration

Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.

1h installs
2
GitHub stars
98
Updated
Nov 6
posthog
Official

investigating-error-issue

Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (/error-tracking/ ) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.

1h installs
2
GitHub stars
98
Updated
Nov 6