Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
Create and push a new semver release tag. An agent skill from ClickHouse/pg_stat_ch.
$ npx skills add ClickHouse/pg_stat_ch --skill create-new-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ClickHouse/pg_stat_ch create-new-release --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/ClickHouse/pg_stat_ch.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-new-release .claude/skills/create-new-release && 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 "create-new-release" agent skill from https://github.com/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-release into .claude/skills/create-new-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-new-release", 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/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-releaseType 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 ClickHouse/pg_stat_ch --skill create-new-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ClickHouse/pg_stat_ch create-new-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/pg_stat_ch.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-new-release .agents/skills/create-new-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-new-release" agent skill from https://github.com/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-release into .agents/skills/create-new-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-new-release", 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 ClickHouse/pg_stat_ch --skill create-new-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ClickHouse/pg_stat_ch create-new-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/pg_stat_ch.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-new-release .cursor/skills/create-new-release && 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 "create-new-release" agent skill from https://github.com/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-release into .cursor/skills/create-new-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-new-release", 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/ClickHouse/pg_stat_ch.git --path .claude/skills/create-new-release--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 ClickHouse/pg_stat_ch --skill create-new-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ClickHouse/pg_stat_ch create-new-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/pg_stat_ch.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-new-release .gemini/skills/create-new-release && 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 "create-new-release" agent skill from https://github.com/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-release into .gemini/skills/create-new-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-new-release", 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 ClickHouse/pg_stat_ch create-new-releaseInstalls 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 ClickHouse/pg_stat_ch --skill create-new-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ClickHouse/pg_stat_ch.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-new-release .github/skills/create-new-release && 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 "create-new-release" agent skill from https://github.com/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-release into .github/skills/create-new-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-new-release", 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 ClickHouse/pg_stat_ch --skill create-new-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ClickHouse/pg_stat_ch create-new-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ClickHouse/pg_stat_ch.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-new-release .opencode/skills/create-new-release && 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 "create-new-release" agent skill from https://github.com/ClickHouse/pg_stat_ch/tree/main/.claude/skills/create-new-release into .opencode/skills/create-new-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-new-release", 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.
create-new-releaseCreate and push a new semver release tag. An agent skill from ClickHouse/pg_stat_ch.
Create New Release is an agent skill from ClickHouse/pg_stat_ch. Create and push a new semver release tag. Asks for release type (patch/minor/major), validates commit exists on remote, bumps version, and pushes the tag.
Its SKILL.md is about 490 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. It works with ClickHouse and PostgreSQL. The licence is Apache-2.0.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 89afc40. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Create New Release loads about 488 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 221 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.
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.
The full file from ClickHouse/pg_stat_ch at commit 89afc40, republished under its Apache-2.0 licence (© ClickHouse). 221 words, ~488 tokens.
.claude/skills/create-new-release/SKILL.md (or your agent's skills folder).Create and push a new semantic version release tag.
Ask release type: Use AskUserQuestion to ask if this is a patch, minor, or major release.
Fetch latest tags from remote:
git fetch --tags originGet the latest semver tag (assumes v prefix like v1.2.3):
git tag --sort=-version:refname -l 'v*' | head -1Parse and bump version based on user selection:
v1.2.3 → v1.2.4v1.2.3 → v1.3.0v1.2.3 → v2.0.0Verify META.json version matches the new tag:
Read META.json and check that both version and provides.pg_stat_ch.version match the new version (without the v prefix). If they don't match, abort and tell the user to update META.json first — PGXN uses this file for the release version.
Validate current commit exists on remote:
git fetch origin
git branch -r --contains HEADIf no remote branch contains HEAD, abort with an error asking the user to push their commits first.
Create and push the tag:
git tag -a <new_version> -m "Release <new_version>"
git push origin <new_version>Report success with the new tag name.
Parse version from tag like v1.2.3:
v prefix. to get major, minor, patch componentsv0.1.0© ClickHouse, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/create-new-release of ClickHouse/pg_stat_ch.
Open the folder on GitHubat commit 89afc40
Create New Release 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 |
|---|---|---|---|---|---|---|
| Create New Release this skillClickHouse/pg_stat_ch | 124 | — | ~488 | Automated safety check: Pass | Apache-2.0 | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Chdb SQLvemetric/vemetric | 394 | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Observal AdminObserval/Observal | 4.2k | — | ~774 | Automated safety check: Pass | Apache-2.0 | |
| Querying Tempotempoxyz/tidx | 107 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Local Platform E2Ecomputesdk/benchmarks | 126 | — | ~3k | Automated safety check: Notes | MIT |
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
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…
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…
tempoxyz/tidx
Query indexed Tempo chain data via tidx HTTP API and CLI. An agent skill from tempoxyz/tidx.
computesdk/benchmarks
Stand up benchmarks-platform locally (Postgres + MinIO + ClickHouse in docker) and run a real @benchsdk/runner benchmark against it, with no cloud or provider credentials.
ClickHouse/agent-skills
MUST USE when investigating performance issues on a ClickHouse-managed Postgres instance.
ClickHouse/pg_stat_ch
Generate C++ header files following Google Style Guide. An agent skill from ClickHouse/pg_stat_ch.
ClickHouse/pg_stat_ch
Check C++ naming conventions against Google Style Guide. An agent skill from ClickHouse/pg_stat_ch.
ClickHouse/pg_stat_ch
Review C++ code against Google C++ Style Guide. An agent skill from ClickHouse/pg_stat_ch.
ClickHouse/pg_stat_ch
Google C++ Style Guide rules for writing clean, maintainable C++ code.
Works with
Categories
Create and push a new semver release tag. An agent skill from ClickHouse/pg_stat_ch. Create New Release is an agent skill from ClickHouse/pg_stat_ch. Create and push a new semver release tag.
Create New Release fits situations like: databases work in your project.
Run `npx skills add ClickHouse/pg_stat_ch --skill create-new-release -a claude-code`. Or copy the skill folder (.claude/skills/create-new-release in ClickHouse/pg_stat_ch) into .claude/skills/create-new-release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ClickHouse/pg_stat_ch --skill create-new-release -a codex`. Or copy the skill folder (.claude/skills/create-new-release in ClickHouse/pg_stat_ch) into .agents/skills/create-new-release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ClickHouse/pg_stat_ch --skill create-new-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-new-release, .gemini/skills/create-new-release, .github/skills/create-new-release and .opencode/skills/create-new-release in your project.
Going by SKILL.md and its folder, Create New Release needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Create New Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 488 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Create New Release: Clickhouse Logs Queries (supabase/supabase, 111k stars), Chdb SQL (vemetric/vemetric, 394 stars), Observal Admin (Observal/Observal, 4.2k stars) and Querying Tempo (tempoxyz/tidx, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ClickHouse (a GitHub organization) maintains it in ClickHouse/pg_stat_ch, which has 124 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: ClickHouse/pg_stat_ch on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.