Official agent skill

Documenting Warehouse Sources

Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source.

OfficialCustom licenceAuto-check passedDatabases

Install Documenting Warehouse Sources

skills CLI

$ npx skills add PostHog/posthog --skill documenting-warehouse-sources -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install PostHog/posthog documenting-warehouse-sources --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/documenting-warehouse-sources .claude/skills/documenting-warehouse-sources && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "documenting-warehouse-sources" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources into .claude/skills/documenting-warehouse-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documenting-warehouse-sources", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add PostHog/posthog --skill documenting-warehouse-sources -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install PostHog/posthog documenting-warehouse-sources --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/documenting-warehouse-sources .agents/skills/documenting-warehouse-sources && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "documenting-warehouse-sources" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources into .agents/skills/documenting-warehouse-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documenting-warehouse-sources", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PostHog/posthog --skill documenting-warehouse-sources -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install PostHog/posthog documenting-warehouse-sources --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/documenting-warehouse-sources .cursor/skills/documenting-warehouse-sources && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "documenting-warehouse-sources" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources into .cursor/skills/documenting-warehouse-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documenting-warehouse-sources", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/PostHog/posthog.git --path .agents/skills/documenting-warehouse-sources

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add PostHog/posthog --skill documenting-warehouse-sources -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install PostHog/posthog documenting-warehouse-sources --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/documenting-warehouse-sources .gemini/skills/documenting-warehouse-sources && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "documenting-warehouse-sources" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources into .gemini/skills/documenting-warehouse-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documenting-warehouse-sources", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install PostHog/posthog documenting-warehouse-sources

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add PostHog/posthog --skill documenting-warehouse-sources -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/documenting-warehouse-sources .github/skills/documenting-warehouse-sources && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "documenting-warehouse-sources" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources into .github/skills/documenting-warehouse-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documenting-warehouse-sources", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PostHog/posthog --skill documenting-warehouse-sources -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install PostHog/posthog documenting-warehouse-sources --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/documenting-warehouse-sources .opencode/skills/documenting-warehouse-sources && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "documenting-warehouse-sources" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/documenting-warehouse-sources into .opencode/skills/documenting-warehouse-sources/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documenting-warehouse-sources", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: documenting-warehouse-sources
GitHub stars: 40k
Token cost: ~1.7k tokens
SKILL.md length: 564 words
Files: 1
Skills in repo: 252
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source.

Works in 3 steps: The doc filename: .md. → The source's docsUrl in… → (implicitly) the listing link — now…
Adding a new source doc
SKILL.md covers The two things the website…, Frontmatter, Canonical template and Shared snippets, plus 2 more sections
Calls python; reaches posthog.com

What it does

Documenting Warehouse Sources is an agent skill from PostHog/posthog, published by the product's own GitHub organization. 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 <SourceParameters / and <SourceTables / components, frontmatter, and the docsUrl/slug rule that prevents 404s.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering Data warehousing. It works with PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…

When your agent uses it

Adding a new source doc
Fixing an inconsistent
Stub source doc
Standardizing the docs at contents/docs/cdp/sources

Example prompts

“/documenting-warehouse-sources”

Requirements

Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

The doc filename: .md.
The source's docsUrl in get_source_config: https://posthog.com/docs/cdp/sources/.
(implicitly) the listing link — now derived from docsUrl, so it follows automatically.

What it can do on your machine

Read from SKILL.md and the folder at commit 812e5c6. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- posthog.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Documenting Warehouse Sources loads about 1.7k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~111
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 564 words (~1,721 tokens).

“User-facing source docs live in the posthog.com repo (not this one) at contents/docs/cdp/sources/.md, served at both /docs/cdp/sources/ and /docs/data-warehouse/sources/. This skill defines the one consistent shape every source doc must follow. Pair it with /implementing-warehouse-sources when shipping a new source.”

— opening of SKILL.md by PostHog, Custom licence

name: documenting-warehouse-sources

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/documenting-warehouse-sources of PostHog/posthog.

Open the folder on GitHubat commit 812e5c6

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.

PostHog/posthog-foss.agents/skills/documenting-warehouse-sources

Compare with similar skills

Documenting Warehouse Sources next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Documenting Warehouse Sources compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Documenting Warehouse Sources this skillPostHog/posthog	40k	—	~1.7k	Automated safety check: Pass	Custom licence	today
Keeper Stress AnalysisClickHouse/ClickHouse	50k	—	~4.7k	Automated safety check: Pass	Apache-2.0	today
Perf ComparisonClickHouse/ClickHouse	50k	—	~3.9k	Automated safety check: Notes	Apache-2.0	today
Patch Release CheckClickHouse/ClickHouse	50k	—	~4k	Automated safety check: Notes	Apache-2.0	today
Clickhouse Architecture Advisorvemetric/vemetric	395	2 repos	~791	Automated safety check: Pass	Apache-2.0	today
Neocarta Add Source Connectorneo4j-labs/neocarta	146	—	~1.9k	Automated safety check: Pass	Apache-2.0	3 days ago

Similar skills

Keeper Stress Analysis
ClickHouse/ClickHouse
Analyze ClickHouse Keeper stress-test results from play.clickhouse.com / keeperstresstests data warehouse.
50k GitHub stars~4.7k tokensUpdated today
DatabasesAuto-check passed
Perf Comparison
ClickHouse/ClickHouse
Evaluate ClickHouse performance test results from existing CI/dashboard data or local perf.py runs.
50k GitHub stars~3.9k tokensUpdated today
DatabasesAuto-check: notes
Patch Release Check
ClickHouse/ClickHouse
Check whether ClickHouse's supported versions (last 3 majors + latest LTS) have recent stable patch releases, diagnose why the scheduled AutoReleases pipeline failed, and identify which releases…
50k GitHub stars~4k tokensUpdated today
DatabasesAuto-check: notes
Clickhouse Architecture Advisor
vemetric/vemetric
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs.
395 GitHub starsUsed in 2 repos~791 tokens
DatabasesAuto-check passed
Neocarta Add Source Connector
neo4j-labs/neocarta
Scaffold, build, and verify a neocarta source or format connector against the connector contract.
146 GitHub stars~1.9k tokensUpdated 3 days ago
DatabasesAuto-check passed
Decompress Binary
ClickHouse/ClickHouse
Extract the inner ELF from a ClickHouse self-extracting clickhouse binary, including when its architecture differs from the host (e.g.
50k GitHub stars~1.1k tokensUpdated today
DatabasesAuto-check passed

Questions about Documenting Warehouse Sources

What does Documenting Warehouse Sources do?

Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source. Documenting Warehouse Sources is an agent skill from PostHog/posthog, published by the product's own GitHub organization.com documentation for a PostHog Data warehouse import source.

When should I use Documenting Warehouse Sources?

Documenting Warehouse Sources fits situations like: adding a new source doc; fixing an inconsistent; stub source doc; standardizing the docs at contents/docs/cdp/sources.

How do I install Documenting Warehouse Sources in Claude Code?

Run `npx skills add PostHog/posthog --skill documenting-warehouse-sources -a claude-code`. Or copy the skill folder (.agents/skills/documenting-warehouse-sources in PostHog/posthog) into .claude/skills/documenting-warehouse-sources in your project. Claude Code loads it when a task matches its description.

How do I install Documenting Warehouse Sources in Codex?

Run `npx skills add PostHog/posthog --skill documenting-warehouse-sources -a codex`. Or copy the skill folder (.agents/skills/documenting-warehouse-sources in PostHog/posthog) into .agents/skills/documenting-warehouse-sources in your project. Codex loads it when a task matches its description.

Can I use Documenting Warehouse Sources in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill documenting-warehouse-sources -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documenting-warehouse-sources, .gemini/skills/documenting-warehouse-sources, .github/skills/documenting-warehouse-sources and .opencode/skills/documenting-warehouse-sources in your project.

What does Documenting Warehouse Sources need to run?

Going by SKILL.md and its folder, Documenting Warehouse Sources needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Documenting Warehouse Sources access the network?

SKILL.md names 1 domain. In commands or code: posthog.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Documenting Warehouse Sources safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Documenting Warehouse Sources use?

Documenting Warehouse Sources has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Documenting Warehouse Sources use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Documenting Warehouse Sources?

Skills that share tags, products or a category with Documenting Warehouse Sources: Keeper Stress Analysis (ClickHouse/ClickHouse, 50k stars), Perf Comparison (ClickHouse/ClickHouse, 50k stars), Patch Release Check (ClickHouse/ClickHouse, 50k stars) and Clickhouse Architecture Advisor (vemetric/vemetric, 395 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documenting Warehouse Sources?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.

Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Documenting Warehouse Sources

Install Documenting Warehouse Sources

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Used in 1 other repository

Compare with similar skills

Similar skills

Keeper Stress Analysis

Perf Comparison

Patch Release Check

Clickhouse Architecture Advisor

Neocarta Add Source Connector

Decompress Binary

More from PostHog/posthog

Authoring Log Alerts

Autoresolving PR Conflicts

Diagnosing Stacktrace Symbolication

Exploring Apm Traces

Exploring LLM Traces

Investigate Metric

Questions about Documenting Warehouse Sources

Install Documenting Warehouse Sources

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from PostHog/posthog

Related

Questions about Documenting Warehouse Sources