Agent skill · posthog
adding-warehouse-person-properties
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 profile. Use when the user wants to "add a person property from my warehouse", "enrich people with Stripe/Postgres/Salesforce data", "put ARR or plan tier on my persons", "target a feature flag by a warehouse column", "sync warehouse columns onto groups or organizations", or wants to inspect, backfill, disable, or debug an existing warehouse-backed person or group property.
What it needs
About 6k tokens when loaded.
What this skill does
Adding warehouse person and group properties A warehouse property mapping reads a synced warehouse table and writes chosen columns onto people or groups. Each row is matched to a person by a distinct ID column, or to a group by a group key column. The mapped columns are then written as ordinary person properties ($set) or group properties ($groupidentify). The result is not a separate kind of property. After the first sync the values behave like any other person or group property, so they work in feature flags, cohorts, insights, surveys, and replay filters. See references/where-they-can-be-used.md for the full surface list and the caveats that matter per surface. In the UI this lives at Data > Warehouse properties, with a Persons tab and a Groups tab. When to use this skill "Add plan tier from my Stripe table to my people" "I want to run a feature flag only for customers with ARR over 50k" "Sync my Postgres accounts table onto organizations" "Why isn't my warehouse property showing up on people?" "Backfill the warehouse property I just added" Use a different skill when: The warehouse source does not exist yet. Connect it first with setting-up-a-data-warehouse-source. The user wants a Customer analytics account property. That target reads a materialized view, not a synced table, and uses savedquery + sourcecolumn instead of the column map below. The user only wants to query warehouse data. Join it in HogQL instead of writing properties onto people. Prerequisites Check these before you start. Each one produces a confusing failure later if it is missing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/skills