Skills.

Give your AI a better way to work.

A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.

Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.

Filter by category

52,958 results · page 46 of 1,766

  • adding-product-alertingSkillCommunication

    Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform. Routes lifecycle state machines, AlertPolicy, destinations, HogFunction dispatch, email, fixed-cadence and calendar scheduling, insight evaluation, the AlertWizard, and shared alert

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • adding-project-secret-api-key-authSkillDev tools

    How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Use when adding PSAK support to a viewset action, allowing a new scope for PSAKs, handling synthetic users (ProjectSecretAPIKeyUser), or choosing PSAK-aware rate throttles. Tr

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • adding-warehouse-person-propertiesSkillDatabases & data

    Sync columns from a synced data warehouse table onto PostHog person or group properties, so warehouse data becomes usable anywhere person and group properties already work: feature flag targeting, cohorts, insight filters and breakdowns, surveys, session replay filters, workflows, and the person pro

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • adopting-generated-api-typesSkillFiles & storage

    Use when migrating frontend code from manual API client calls (`api.get`, `api.create`, `api.surveys.get`, `api.dashboards.list`, `new ApiRequest()`) and handwritten TypeScript interfaces to generated API functions and types. Triggers on files importing from `lib/api`, files with `api.get<`, `api.cr

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • analyzing-expensive-usersSkillMonitoring & ops

    Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • analyzing-experiment-precompute-canarySkillMonitoring & ops

    Analyze the experiment precompute result-consistency canary across prod-US and prod-EU, deep-dive any issues, and produce an actionable report. Sweeps the canary's Prometheus health gauges in both regions, and when anything is unhealthy pulls the structured divergence/failure logs from Loki to recon

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • analyzing-experiment-query-performanceSkillDev tools

    Pull and interpret production experiment query-performance data from the staff-only `/api/debug_ch_queries` endpoints backing the `/experiments/staff` scene: slowest experiment queries, precompute read/build health, and preaggregation cache footprint. Covers prod-US and prod-EU via a `query_performa

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • analyzing-experiment-session-replaysSkillDev tools

    Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • analyzing-insights-across-teamsSkillWeb & browsing

    Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide ins

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • announcing-behavior-changesSkillMonitoring & ops

    Decides whether a behavior-changing fix needs an in-app notice, then builds one that reaches only the affected users and can be removed later. Use when a change alters what an existing user sees without them doing anything — a metric moves, a chart shifts, a count drops, a date range resolves differ

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • auditing-endpointsSkillDev tools

    Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks "what endpoints can I clean up?", "are any of my endpoints broken?", "which materialised versions are still being called?", or wants a one-shot cleanup pass over

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • auditing-llm-gateway-paritySkillAI & models

    Audits services/llm-gateway against PostHog/ai-gateway and updates services/llm-gateway/PARITY.md from current implementation evidence. Use when either gateway changes auth, attribution, billing, endpoints, providers, models, routing, or metadata; when reviewing a Python gateway change; or when aske

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • auditing-warehouse-source-coverageSkillDatabases & data

    Audit already-implemented Data warehouse import sources for endpoints, schemas, and tables the vendor's API offers but we never wired up. Use when asked whether a source is missing endpoints, to find new endpoints a vendor has added since a source was built, to refresh COVERAGE_GAPS.md, to prioritiz

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • auditing-warehouse-view-healthSkillFiles & storage

    Audit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks "which of my views are broken?", "why is this materialized view failing?", "are any of my v

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • authoring-ci-workflowsSkillDev tools

    Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under `.github/` — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, `timeout-minutes`, `paths` filters, caching, or runner choice. Covers Pos

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • authoring-data-quality-checksSkillAI & models

    Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Use when asked to test a model, validate a view, check for nulls or duplic

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • authoring-error-tracking-alertsSkillCommunication

    Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedu

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • autoresolving-pr-conflictsSkillAI & models

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source conflicts with judgment), land one merge commit on the PR head, and flag everything else for a human. Use wh

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • building-a-dashboardSkillMonitoring & ops

    Build a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics/charts together on one page, assemble a dashboard for a topic (product analy

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • building-canvasesSkillWeb & browsing

    Create or edit a PostHog freeform canvas — a sandboxed browser application (data board, document, form, small tool, graphics experiment) stored in PostHog and rendered by the desktop/web app. Use when a task asks to build, generate, update, or fix a standalone canvas app, or when a freeform canvas i

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • building-html-canvasesSkillWeb & browsing

    Author a PostHog canvas with semantic HTML, CSS, and direct browser APIs — documents, articles, generative graphics, 2D canvas and WebGL experiences, and focused experiments where React components add no useful structure. Use after building-canvases has routed a canvas request to a plain-HTML/browse

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • building-product-empty-statesSkillDev tools

    Guide for adding a product setup empty state — the skippable first-run screen a product scene shows until real data arrives, built on the shared ProductEmptyState component. Use when adding an empty state or first-run/setup screen to a product scene, declaring `emptyState` on a `SceneExport`, writin

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • building-react-quill-canvasesSkillMedia

    Author the React + Quill implementation of a PostHog canvas: the single-component contract, the allowed imports, Quill (PostHog's design system) component and composition rules, theme-aware design tokens, loading skeletons, and the in-canvas date picker. Use after building-canvases has routed a canv

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • cleaning-up-stale-feature-flagsSkillDev tools

    Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • clickhouse-migrationsSkillDatabases & data

    ClickHouse migration patterns and rules. Use when creating or modifying ClickHouse migrations.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • composing-grid-canvasesSkillProductivity

    Compose PostHog grid canvases — widget grids (including the user's home canvas) built from reusable component canvases. Use when a task asks to add, fill, move, resize, or remove a widget on a grid or home canvas, to compose a whole canvas of widgets from one ask, to build a reusable widget/componen

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • configuring-experiment-analyticsSkillDatabases & data

    Configures the analytics side of a PostHog experiment — exposure criteria (server-resolved default exposure event vs custom exposure events), primary and secondary metrics, the supported metric types (count, sum, ratio with `math` and `math_property`, retention with `retention_window_start` and `sta

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • configuring-experiment-rolloutSkillDev tools

    Configures the rollout shape of a PostHog experiment — the variant split (50/50, 80/20, A/B/C ratios), the overall rollout percentage that gates how many users enter the experiment, and the disambiguation when a percentage like "roll out to 25%" could mean either. Use when the user mentions a rollou

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • consuming-endpoints-from-client-codeSkillDev tools

    Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materiali

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • context-layer-consolidationSkillDocs & knowledge

    Keep the context wiki coherent using the deterministic lint report queue

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details

What is a skill?

A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.

52,524 of the 52,958 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.

Install one and every AI you use gets it

Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.

Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.

See how to connect your AI