Clickhouse Managed Postgres Rca
ClickHouse/agent-skills
MUST USE when investigating performance issues on a ClickHouse-managed Postgres instance.
Runs read-only production database analysis through PostHog's internal Metabase instances.
Install Querying Production Databases Via Metabase
$ npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog querying-production-databases-via-metabase --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/querying-production-databases-via-metabase .claude/skills/querying-production-databases-via-metabase && rm -rf skills-srcUse ~/.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/
Install the "querying-production-databases-via-metabase" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabase into .claude/skills/querying-production-databases-via-metabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-production-databases-via-metabase", 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 install https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabaseType 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.
$ npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog querying-production-databases-via-metabase --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/querying-production-databases-via-metabase .agents/skills/querying-production-databases-via-metabase && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "querying-production-databases-via-metabase" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabase into .agents/skills/querying-production-databases-via-metabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-production-databases-via-metabase", 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.
$ npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog querying-production-databases-via-metabase --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/querying-production-databases-via-metabase .cursor/skills/querying-production-databases-via-metabase && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "querying-production-databases-via-metabase" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabase into .cursor/skills/querying-production-databases-via-metabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-production-databases-via-metabase", 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 https://github.com/PostHog/posthog.git --path .agents/skills/querying-production-databases-via-metabase--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog querying-production-databases-via-metabase --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/querying-production-databases-via-metabase .gemini/skills/querying-production-databases-via-metabase && rm -rf skills-srcUse ~/.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/
Install the "querying-production-databases-via-metabase" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabase into .gemini/skills/querying-production-databases-via-metabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-production-databases-via-metabase", 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.
$ gh skill install PostHog/posthog querying-production-databases-via-metabaseInstalls 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).
$ npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/querying-production-databases-via-metabase .github/skills/querying-production-databases-via-metabase && rm -rf skills-srcUse ~/.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/
Install the "querying-production-databases-via-metabase" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabase into .github/skills/querying-production-databases-via-metabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-production-databases-via-metabase", 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.
$ npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog querying-production-databases-via-metabase --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/querying-production-databases-via-metabase .opencode/skills/querying-production-databases-via-metabase && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "querying-production-databases-via-metabase" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/querying-production-databases-via-metabase into .opencode/skills/querying-production-databases-via-metabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-production-databases-via-metabase", 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
querying-production-databases-via-metabase- GitHub stars
- 40k
- Token cost
- ~2.8k tokens
- SKILL.md length
- 924 words
- Files
- 1
- Skills in repo
- 254
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Runs read-only production database analysis through PostHog's internal Metabase instances.
- Works in 2 steps: Discover the current ClickHouse DB ID:… → Pass that ID into hogli metabase:query.…
- ClickHouse query logs
- SKILL.md covers Environment, Authentication, Running a ClickHouse query and ClickHouse: what counts as a…, plus 5 more sections
- Calls python3; reaches metabase.prod-us.posthog.dev and metabase.prod-eu.posthog.dev
What it does
Querying Production Databases Via Metabase is an agent skill from PostHog/posthog, published by the product's own GitHub organization. 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 patterns for both engines.
Its SKILL.md is about 2.8k 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 Query optimization, Data warehousing and Authentication. It works with PostHog, ClickHouse and PostgreSQL. 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
- ClickHouse query logs
- Slow query cost
- Postgres query plans
- Index selection
Example prompts
- “/querying-production-databases-via-metabase”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Discover the current ClickHouse DB ID: hogli metabase:databases --region .
- Pass that ID into hogli metabase:query. Pipe SQL via stdin or --file.
What it can do on your machine
Read from SKILL.md and the folder at commit c012c8d. 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:
python3
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:
metabase.prod-us.posthog.devmetabase.prod-eu.posthog.dev
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
Querying Production Databases Via Metabase loads about 2.8k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 924 words of instructions outside code blocks.
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 924 words (~2,830 tokens).
“PostHog's production databases are reachable for ad-hoc, read-only analysis through internal Metabase instances. Both Metabases sit behind an AWS ALB with Cognito OAuth, so authentication is SSO-gated — Metabase API keys alone won't work.”
- name
- querying-production-databases-via-metabase
Files
Just SKILL.md in .agents/skills/querying-production-databases-via-metabase of PostHog/posthog.
Open the folder on GitHubat commit c012c8d
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.
Compare with similar skills
Querying Production Databases Via Metabase 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Querying Production Databases Via Metabase this skillPostHog/posthog | 40k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Clickhouse Managed Postgres RcaClickHouse/agent-skills | 545 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Chdb SQLvemetric/vemetric | 395 | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| PR Triagewannabespace/conar | 1.5k | — | ~811 | Automated safety check: Pass | AGPL-3.0 | |
| Observal AdminObserval/Observal | 4.3k | — | ~774 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
Chdb SQL
vemetric/vemetric
A skill your agent uses when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse…
PR Triage
wannabespace/conar
Speed up a GitHub PR review — sort every changed file into trivial / skim / review, mark the trivial ones as viewed on GitHub, and hand back a reading order for the rest.
Observal Admin
Observal/Observal
Administers Observal users, settings, diagnostics, review queues, security events, audit logs, SAML, SCIM, the local Observal server, its upgrades and rollback, and its own PostgreSQL and ClickHouse…
Clickhouse System Queries
FrankChen021/datastoria
Query ClickHouse system tables to inspect query logs, monitor cluster health, check replication status, and analyze slow queries.
More from PostHog/posthog
All 254 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Querying Production Databases Via Metabase
What does Querying Production Databases Via Metabase do?
Runs read-only production database analysis through PostHog's internal Metabase instances. Querying Production Databases Via Metabase is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Runs read-only production database analysis through PostHog's internal Metabase instances.
When should I use Querying Production Databases Via Metabase?
Querying Production Databases Via Metabase fits situations like: clickHouse query logs; slow query cost; postgres query plans; index selection.
How do I install Querying Production Databases Via Metabase in Claude Code?
Run `npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a claude-code`. Or copy the skill folder (.agents/skills/querying-production-databases-via-metabase in PostHog/posthog) into .claude/skills/querying-production-databases-via-metabase in your project. Claude Code loads it when a task matches its description.
How do I install Querying Production Databases Via Metabase in Codex?
Run `npx skills add PostHog/posthog --skill querying-production-databases-via-metabase -a codex`. Or copy the skill folder (.agents/skills/querying-production-databases-via-metabase in PostHog/posthog) into .agents/skills/querying-production-databases-via-metabase in your project. Codex loads it when a task matches its description.
Can I use Querying Production Databases Via Metabase 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 querying-production-databases-via-metabase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/querying-production-databases-via-metabase, .gemini/skills/querying-production-databases-via-metabase, .github/skills/querying-production-databases-via-metabase and .opencode/skills/querying-production-databases-via-metabase in your project.
What does Querying Production Databases Via Metabase need to run?
Going by SKILL.md and its folder, Querying Production Databases Via Metabase needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Querying Production Databases Via Metabase access the network?
SKILL.md names 2 domains. In commands or code: metabase.prod-us.posthog.dev and metabase.prod-eu.posthog.dev; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Querying Production Databases Via Metabase 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 Querying Production Databases Via Metabase use?
Querying Production Databases Via Metabase 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 Querying Production Databases Via Metabase use?
About 2.8k tokens (SKILL.md is roughly 11k 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 Querying Production Databases Via Metabase?
Skills that share tags, products or a category with Querying Production Databases Via Metabase: Clickhouse Managed Postgres Rca (ClickHouse/agent-skills, 545 stars), Clickhouse Logs Queries (supabase/supabase, 111k stars), Chdb SQL (vemetric/vemetric, 395 stars) and PR Triage (wannabespace/conar, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Querying Production Databases Via Metabase?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 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.