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

55,543 results · page 51 of 1,852

  • querying-tophogSkillDatabases & data

    Query tophog — the ingestion pipeline's heavy-hitter store in ClickHouse — to identify hot or expensive actors (team_id, distinct_id, session_id, partition) during incident triage. Use when investigating ingestion lag, a hot or lagging Kafka partition, expensive person processing, merge storms, or a

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • reviewing-personhog-protocolSkillDev tools

    The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog co

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • reviewing-with-coderabbitSkillDev tools

    Run a CodeRabbit review over the branch from the terminal, with the `coderabbit` CLI, and record the pass in the PR description. Use before `gh pr create`, and whenever a review of a branch is asked for: a local review, a self-review, a CodeRabbit review, or a pre-PR review. Run it once per branch.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • running-ci-preflightSkillProductivity

    Catch the deterministic CI failures reachable from your diff before pushing, with `hogli ci:preflight`. Use when the pre-push hook blocks a push, before reporting a task done, or after editing Python, serializers, migrations, workflows, or dependency manifests — to avoid burning a CI matrix on a fai

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • scene-menu-barSkillDev tools

    Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>. Use when adding new menu items, moving items between menus, gating behind feature flags, building a new scene's menubar, or wiring rich inputs (tags, combobox) into the bar.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • security-auditSkillFiles & storage

    Focused security audit of code, calibrated to surface real exploitable bugs and suppress theoretical findings. Use when the user asks to "audit", "security-audit", "find vulnerabilities", "check for IDOR/SSRF/XSS/injection", or wants a security review of a file, directory, branch diff, or PR. Covers

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • sending-notificationsSkillCommunication

    How to send real-time in-app notifications from PostHog backend code. Use when integrating notifications into a new feature, wiring up a notification source (alerts, comments, approvals, pipelines, issues), or choosing the right target type and priority for a notification.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setting-feature-flags-in-storybookSkillDev tools

    Use when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants. Covers the `featureFlags` story parameter and why imperatively setting flags renders the flag-off branch in visual-regression snapshots while passing in jest.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setting-up-data-catalogSkillMonitoring & ops

    Populates and maintains a project's data catalog (semantic layer): canonical metrics, trust marks (certifications) on warehouse tables/views, and reviewed table relationships. Use when asked to set up / seed / bootstrap the data catalog or semantic layer, to catalog a project's metrics, to certify o

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setting-up-devboxSkillAI & models

    Guide a PostHog engineer through spinning up, connecting to, running commands on, and mirroring local code to a remote devbox (a Coder workspace running the full PostHog stack). Use when asked to set up a devbox, start or connect to a devbox, configure remote dev, get gh CLI / Claude Code authed on

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setting-up-support-slack-locallySkillCommunication

    Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Use when the user wants to test the conversations Slack integration locally, hits "Support Slack OAuth client ID is not configured", gets a white s

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setting-up-warehouse-propertiesSkillDatabases & data

    Populate person or group properties from a data warehouse table or materialized view, so warehouse columns become properties usable in feature flags, cohorts, and insights. Use when the user wants to "sync my Postgres columns to person properties", "map a warehouse table to people", "replace our dai

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setup-web-testsSkillAI & models

    Set up Python test environment in Claude Code for web where flox is unavailable. Use when you need to run backend tests and `uv sync` fails due to Python version mismatch.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • splitting-oversized-modulesSkillFiles & storage

    Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a huma

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • stacking-prsSkillDev tools

    Create and manage GitHub native Stacked PRs in this repo with the `gh stack` CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers cr

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • suppressing-noisy-errorsSkillWeb & browsing

    Create PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks "stop capturing this error", "drop browser extension errors", "ignore ResizeObserver loops", "suppress bot-driven errors", or wants to reduce ingestion cost from noisy unactiona

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • survey-sdk-auditSkillDev tools

    Audit PostHog survey SDK features and version requirements

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • testing-mcp-tools-locallySkillDev tools

    Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end. Use when testing batch import support tooling, debugging MCP tool responses or discovery (tools not appearing),

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • triaging-error-issuesSkillDev tools

    Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issue

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • triaging-warehouse-sync-ticketsSkillDatabases & data

    Debug a customer's data warehouse source, schema, or table from a support ticket, using PostHog's own production data. Use when a ticket says a warehouse table is stale, empty, stuck, duplicated, missing rows, or failing to sync, and you need the real state of the sync rather than the customer's des

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • triaging-web-analytics-supportSkillDatabases & data

    Triage web analytics support tickets end to end: enumerate open tickets from the in-app conversations product and their Zendesk mirrors, classify each into a diagnostic shape (frontend crash, "two numbers don't match", traffic count drop, tracker not loading / undercounting vs a competitor, ad-platf

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • turning-engineering-analytics-into-insightsSkillDatabases & data

    Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • understanding-billing-usageSkillMonitoring & ops

    Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • using-kea-disposablesSkillDocs & knowledge

    Use when adding timers (`setInterval`, `setTimeout`), event listeners (`window.addEventListener`, `document.addEventListener`, `MediaQueryList.addEventListener`), or any other resource that needs cleanup inside a kea logic. Every logic has `cache.disposables.add(setup, key?, options?)` and `cache.di

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • using-redis-token-bucketsSkillDatabases & data

    Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. `posthog/token_bucket.py` provides an atomic Lua token buc

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • validating-and-publishing-canvasesSkillDev tools

    Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, a

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • visualizing-change-over-timeSkillDatabases & data

    Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcp_analytics frontend, custom visualizations). Use when a use

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • warehouse-source-new-versionSkillDatabases & data

    Add support for a new vendor API version to an existing Data warehouse import source, or deprecate an old one. Use when a vendor ships a new API version (Stripe date versions, Shopify quarterly versions, header-pinned revisions, /vN/ URL bumps), when implementing a version-update or deprecation task

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • working-with-chartsSkillDev tools

    Guides consumers of @posthog/quill-charts through chart selection, data, themes, sizing, and composition. Use when adding or changing a chart built with the package, including its axes, tooltips, legend, overlays, or interactions. Links to package examples and API docs. Does not cover product integr

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • writing-clickhouse-queriesSkillDatabases & data

    Guide for writing performant ClickHouse queries in PostHog product code. Use when writing HogQL query runners, designing a ClickHouse table for a new product, adding materialized columns or skip indexes, or choosing a row ID format. For optimizing an existing query that is already too slow, use `/op

    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.

55,111 of the 55,543 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