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.
Category: Databases & data
2,461 results · page 3 of 83
- View details
insforgeSkillDatabases & data
Lets your agent write app code using InsForge for databases, logins, file storage, payments, emails, and AI features.
Ready to connect
- View details
nature-dataSkillDatabases & data
Lets your agent draft and check Nature-ready data availability statements, dataset citations, and FAIR metadata checklists.
Ready to connect★ 41k
- View details
adding-personhog-rpcSkillDatabases & data
Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when addin
Ready to connect★ 40k
- 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
- 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
- View details
clickhouse-migrationsSkillDatabases & data
ClickHouse migration patterns and rules. Use when creating or modifying ClickHouse migrations.
Ready to connect★ 40k
- View details
debugging-mcp-analyticsSkillDatabases & data
Debug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the `@posthog/mcp` and `posthog.mcp` SDKs plus the mcp_analytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are missing", "per-tool
Ready to connect★ 40k
- View details
debugging-signals-pipelineSkillDatabases & data
Debug the signals pipeline locally end-to-end. Covers emitting test signals from fixtures, monitoring Temporal workflows via the REST API, reading sandbox agent logs from object storage, inspecting Docker sandbox containers, and diagnosing common failures (stale ClickHouse embeddings, agentsh networ
Ready to connect★ 40k
- View details
diagnosing-ci-and-merge-bottlenecksSkillDatabases & data
Diagnoses CI and pull-request pipeline health for a GitHub repo using the engineering analytics MCP tools — pull-requests (PR list with CI status), workflow-health (per-workflow CI trends), and pr-lifecycle (a single PR's timeline). Use when asked whether CI is getting faster or slower, which GitHub
Ready to connect★ 40k
- View details
django-migrationsSkillDatabases & data
Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDat
Ready to connect★ 40k
- View details
documenting-warehouse-sourcesSkillDatabases & data
Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source. Use when adding a new source doc, fixing an inconsistent or stub source doc, or standardizing the docs at contents/docs/cdp/sources. Covers the canonical template, shared snippets, the auto-rendered
Ready to connect★ 40k
- View details
generating-clickhouse-query-performance-reportsSkillDatabases & data
Produce and structure slow-query performance reports for PostHog's production ClickHouse (US and EU). Use when asked for a slow query report, query performance analysis over the last N days, per-team query cost, OOM or timeout investigation, cluster cost/memory regressions, or materialization candid
Ready to connect★ 40k
- View details
implementing-warehouse-sourcesSkillDatabases & data
Implement and extend PostHog Data warehouse import sources. Use when adding a new source under products/warehouse_sources/backend/temporal/data_imports/sources, adding datasets/endpoints to an existing source, or adding incremental sync, resumable imports, webhook ingestion, pagination, credentials
Ready to connect★ 40k
- View details
monitoring-capture-serviceSkillDatabases & data
Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production. Use when investigating latency, event loss, Kafka backpressure, Redis issues, rate limiting, Envoy proxy issues, or any capture health question. Covers prod-us and prod-eu environments.
Ready to connect★ 40k
- View details
monitoring-ingestion-pipelineSkillDatabases & data
Guide for using the Grafana MCP to monitor and diagnose the Node.js ingestion pipeline workers in production. Use when investigating event lag, drops, pipeline errors, person/group processing, Kafka consumer health, Redis, Postgres, ClickHouse downstream health, or any ingestion worker question. Cov
Ready to connect★ 40k
- View details
optimizing-clickhouse-and-hogql-queriesSkillDatabases & data
Workflow for optimizing ClickHouse and HogQL queries. Use when a HogQL query, query runner, insight, or report is too slow; when a hand-written ClickHouse query (via `sync_execute` or in a migration) is too slow; when ClickHouse times out or hits memory limits; when investigating a slow `system.quer
Ready to connect★ 40k
- View details
profiling-slow-api-endpointsSkillDatabases & data
Profiles slow PostHog API endpoints when the main cost is in Postgres or Python. Use when a screen, picker, or list is slow; a Django endpoint has high tail latency; a query plan changes with tenant size; or a proposed database fix needs production evidence. Covers APM traces, safe production EXPLAI
Ready to connect★ 40k
- View details
querying-local-postgresSkillDatabases & data
Run read-only SQL against the local Postgres app database (SELECT, EXPLAIN, EXPLAIN ANALYZE on SELECT). Default local URL postgres://posthog:posthog@localhost:5432/posthog; else DATABASE_URL. Use when querying the local DB, inspecting tables, debugging data, or analyzing query plans. Mutations are s
Ready to connect★ 40k
- View details
querying-production-databases-via-metabaseSkillDatabases & data
Runs read-only production database analysis through PostHog's internal Metabase instances. Use for ClickHouse query logs, slow query cost, Postgres query plans, index selection, or tenant-size analysis. Covers US and EU database discovery, SSO login through `hogli`, safe query rules, and query patte
Ready to connect★ 40k
- View details
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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- View details
writing-code-commentsSkillDatabases & data
Gates whether a code comment should exist and forces the ones that stay to explain why, not what. Use ALWAYS before writing or editing a comment in any language (Python, TypeScript, Go, Rust, SQL), and when reviewing a diff that adds comments. Removes the comment types that clutter the codebase: nar
Ready to connect★ 40k
- View details
dataset-curationSkillDatabases & data
Lets your agent prepare, format, and validate datasets for fine-tuning language models.
Ready to connect★ 40k
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.
54,764 of the 55,196 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.