Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result.
Install Bump Up Ducklake
$ npx skills add relytcloud/pg_ducklake --skill bump-up-ducklake -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install relytcloud/pg_ducklake bump-up-ducklake --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/relytcloud/pg_ducklake.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bump-up-ducklake .claude/skills/bump-up-ducklake && 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 "bump-up-ducklake" agent skill from https://github.com/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklake into .claude/skills/bump-up-ducklake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-up-ducklake", 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/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklakeType 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 relytcloud/pg_ducklake --skill bump-up-ducklake -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install relytcloud/pg_ducklake bump-up-ducklake --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/relytcloud/pg_ducklake.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/bump-up-ducklake .agents/skills/bump-up-ducklake && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bump-up-ducklake" agent skill from https://github.com/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklake into .agents/skills/bump-up-ducklake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-up-ducklake", 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 relytcloud/pg_ducklake --skill bump-up-ducklake -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install relytcloud/pg_ducklake bump-up-ducklake --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/relytcloud/pg_ducklake.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/bump-up-ducklake .cursor/skills/bump-up-ducklake && 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 "bump-up-ducklake" agent skill from https://github.com/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklake into .cursor/skills/bump-up-ducklake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-up-ducklake", 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/relytcloud/pg_ducklake.git --path .agents/skills/bump-up-ducklake--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 relytcloud/pg_ducklake --skill bump-up-ducklake -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install relytcloud/pg_ducklake bump-up-ducklake --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/relytcloud/pg_ducklake.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/bump-up-ducklake .gemini/skills/bump-up-ducklake && 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 "bump-up-ducklake" agent skill from https://github.com/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklake into .gemini/skills/bump-up-ducklake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-up-ducklake", 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 relytcloud/pg_ducklake bump-up-ducklakeInstalls 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 relytcloud/pg_ducklake --skill bump-up-ducklake -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/relytcloud/pg_ducklake.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/bump-up-ducklake .github/skills/bump-up-ducklake && 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 "bump-up-ducklake" agent skill from https://github.com/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklake into .github/skills/bump-up-ducklake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-up-ducklake", 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 relytcloud/pg_ducklake --skill bump-up-ducklake -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install relytcloud/pg_ducklake bump-up-ducklake --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/relytcloud/pg_ducklake.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/bump-up-ducklake .opencode/skills/bump-up-ducklake && 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 "bump-up-ducklake" agent skill from https://github.com/relytcloud/pg_ducklake/tree/main/.agents/skills/bump-up-ducklake into .opencode/skills/bump-up-ducklake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-up-ducklake", 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
bump-up-ducklake- GitHub stars
- 143
- Token cost
- ~1.3k tokens
- SKILL.md length
- 633 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result.
- Works in 4 steps: Read the repository rules → Rebase the patch series → Account for upstream tests → …
- Every pgducklake/thirdparty/ducklake bump
- SKILL.md covers 1. Read the repository rules, 2. Rebase the patch series, 3. Account for upstream tests and 4. Validate
- Runs Python scripts from its folder; calls make, git and python3
What it does
Bump Up Ducklake is an agent skill from relytcloud/pg_ducklake. Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result. Use for every pgducklake/thirdparty/ducklake bump.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/check-test-inventory.py`).
It sits in Databases. It works with SQL and PostgreSQL. The repository describes itself as: Native lakehouse experience in Postgres powered by DuckDB & Ducklake. The licence is MIT.
When your agent uses it
- Every pgducklake/thirdparty/ducklake bump
Example prompts
- “/bump-up-ducklake”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit bc5d4b4. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
makegitpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
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.
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
Bump Up Ducklake loads about 1.3k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 633 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); the scripts in this folder are not scanned.
SKILL.md
The full file from relytcloud/pg_ducklake at commit bc5d4b4, republished under its MIT licence (© relytcloud). 633 words, ~1,322 tokens.
Download SKILL.mdSave it as
.claude/skills/bump-up-ducklake/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- bump-up-ducklake
- description
- Safely bump pg_ducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result. Use for every pg_ducklake/third_party/ducklake bump.
Bump Up DuckLake
Follow this playbook in order. Stop rather than overwrite unexplained work.
1. Read the repository rules
Read AGENTS.md, the setup-dev and commit-and-pr-guidelines skills, and
pg_ducklake/Makefile. Obtain an explicit target DuckLake ref and resolve the
old and new revisions to full commit SHAs.
Before changing anything, inspect the superproject and submodule status. The
DuckLake checkout is normally dirty because the Makefile applies
third_party/ducklake-NNN-*.patch and creates .patched. Do not assume all dirt
is generated: verify it against the current patch series. Never discard, clean,
stash, or overwrite unrelated user changes.
2. Rebase the patch series
Use a disposable DuckLake worktree, not the build checkout.
- At the old revision, apply every patch in Makefile lexical order and commit each patch separately.
- Rebase that commit stack onto the target revision. Resolve conflicts in the patch that owns the change.
- If upstream absorbed a patch, prove the rebased commit is empty before removing it. Do not silently drop or squash patches.
- Export the rebased commits back to the ordered patch files.
- In a fresh worktree at the target revision, run
git apply --checkand apply the complete series in Makefile order. Compare its aggregate diff with the rebased stack. - Update the superproject gitlink only after the clean-room application passes.
Local pg_ducklake changes belong in patch files, never in a commit inside the
DuckLake submodule. Do not commit .patched or patched submodule worktree files.
Use the next unused three-digit prefix for a new patch; preserve existing patch
names and ordering unless a deliberate renumber is reviewed.
3. Account for upstream tests
The authoritative inventory is every tracked target-revision file matching
test/sql/**/*.test or test/sql/**/*.test_slow. Run:
python3 .agents/skills/bump-up-ducklake/scripts/check-test-inventory.pyThe checker requires every upstream test to be exactly one of:
- mapped by an exact first-line
Upstream: test/sql/...marker underpg_ducklake/test/regression/sql/ducklakeorpg_ducklake/test/isolation/specs/ducklake; or - listed in this skill's
unmapped-tests.tsvwith a concrete reason.
It also checks source/expected pairs and default schedule coverage. Review
git diff --name-status -M OLD NEW -- test/sql separately so modified, renamed,
and deleted upstream tests are not overlooked.
Show full SKILL.md (295 more words)Show less
Newly added tests
Map every newly added upstream test unless a genuine PostgreSQL-specific blocker makes that impossible. Port behavior and invariants, not DuckDB syntax:
- mirror
test/sql/<path>.testastest/regression/sql/ducklake/<path>.sql, or use an isolation spec for real concurrency; - preserve the exact upstream path in the first line;
- create and review the matching expected output;
- use unique objects, deterministic ordering, dynamic IDs, and complete cleanup;
- do not bless accidental errors or weaken physical/conflict invariants;
- add the mapped name to the corresponding default schedule.
If a test cannot be mapped, add one sorted row to unmapped-tests.tsv. The
reason must identify the exact unavailable API, semantic mismatch, external
requirement, or redundant local coverage. Do not use only unsupported,
not applicable, slow, or TODO. pending_port exists only for the legacy
backlog recorded when this inventory was introduced; do not assign it to tests
added by a later bump.
TSV columns are:
upstream_path: exact unique path at the target revision;reason_code:pending_port,unsupported,inapplicable,external_dependency,resource_intensive,platform_specific,redundant, orblocked;reason: one concrete ASCII line without tabs.
Remove a TSV row when its test is mapped or deleted upstream. Update paths for
upstream renames. The inventory must remain sorted by upstream_path.
4. Validate
After removing the stale .patched stamp, build from clean inputs. Use an
available supported PG_CONFIG; stop and ask if none exists. On macOS, apply
the LIBRARY_PATH prefix from AGENTS.md.
Run, at minimum:
python3 .agents/skills/bump-up-ducklake/scripts/check-test-inventory.py
PG_CONFIG=<pg_config> make check-format
PG_CONFIG=<pg_config> make -j"$(nproc 2>/dev/null || sysctl -n hw.ncpu)"
PG_CONFIG=<pg_config> make install
PG_CONFIG=<pg_config> make check-regression
PG_CONFIG=<pg_config> make check-isolation
git diff --checkRun focused tests while developing, but full scheduled regression and isolation runs are mandatory. Validate both the oldest and newest available supported PostgreSQL versions; state clearly which matrix entries were not run.
Finally inspect git diff --submodule=log and status. Stage explicit paths only.
The gitlink, rebased patches, test mappings, expected outputs, schedules, and TSV
updates belong in one atomic commit. Do not commit or push unless requested.
© relytcloud, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts) in .agents/skills/bump-up-ducklake of relytcloud/pg_ducklake.
- SKILL.md
- scripts/check-test-inventory.py
- unmapped-tests.tsv
Open the folder on GitHubat commit bc5d4b4
Compare with similar skills
Bump Up Ducklake 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 |
|---|---|---|---|---|---|---|
| Bump Up Ducklake this skillrelytcloud/pg_ducklake | 143 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Citus Check Style Reindentcitusdata/citus | 13k | — | ~1.5k | Automated safety check: Notes | AGPL-3.0 | |
| Safe SQL Executionsupabase/supabase | 111k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Citus Backportcitusdata/citus | 13k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| SQL Database Support for pRESTprest/prest | 4.6k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Citus Check Style Reindent
citusdata/citus
Fix a failing citusdata/citus check-style job by running make reindent with the exact uncrustify/citusindent versions the currently checked-out branch pins (read from its own STYLEGUIDE.md and its…
- Official
Safe SQL Execution
supabase/supabase
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
Citus Backport
citusdata/citus
Backport one or more merged citusdata/citus main commits/PRs onto the active release branches.
SQL Database Support for pREST
prest/prest
Guides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects.
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…
More from relytcloud/pg_ducklake
Setup Dev
relytcloud/pg_ducklake
Dev environment setup for build tools, PostgreSQL, submodules, and worktrees.
Commit And PR Guidelines
relytcloud/pg_ducklake
Commit message conventions and pull request description guidelines.
Version Management
relytcloud/pg_ducklake
Versioning, branch, and release policy (semantic versioning, branch-per-minor, tag-per-patch).
Related
Works with
Categories
Questions about Bump Up Ducklake
What does Bump Up Ducklake do?
Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result. Bump Up Ducklake is an agent skill from relytcloud/pg_ducklake. Safely bump pgducklake's vendored DuckLake commit, rebase its patch series, account for newly added upstream SQLLogicTests, update mapped test schedules, and validate the result.
When should I use Bump Up Ducklake?
Bump Up Ducklake fits situations like: every pgducklake/thirdparty/ducklake bump.
How do I install Bump Up Ducklake in Claude Code?
Run `npx skills add relytcloud/pg_ducklake --skill bump-up-ducklake -a claude-code`. Or copy the skill folder (.agents/skills/bump-up-ducklake in relytcloud/pg_ducklake) into .claude/skills/bump-up-ducklake in your project. Claude Code loads it when a task matches its description.
How do I install Bump Up Ducklake in Codex?
Run `npx skills add relytcloud/pg_ducklake --skill bump-up-ducklake -a codex`. Or copy the skill folder (.agents/skills/bump-up-ducklake in relytcloud/pg_ducklake) into .agents/skills/bump-up-ducklake in your project. Codex loads it when a task matches its description.
Can I use Bump Up Ducklake 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 relytcloud/pg_ducklake --skill bump-up-ducklake -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-up-ducklake, .gemini/skills/bump-up-ducklake, .github/skills/bump-up-ducklake and .opencode/skills/bump-up-ducklake in your project.
What does Bump Up Ducklake need to run?
Going by SKILL.md and its folder, Bump Up Ducklake needs Python for the scripts in its folder and the command-line tools its instructions call (make, git and python3). Our summary lists: Python 3.
Does Bump Up Ducklake access the network?
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.
Is Bump Up Ducklake 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Bump Up Ducklake use?
Bump Up Ducklake is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bump Up Ducklake use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Bump Up Ducklake?
Skills that share tags, products or a category with Bump Up Ducklake: Clickhouse Logs Queries (supabase/supabase, 111k stars), Citus Check Style Reindent (citusdata/citus, 13k stars), Safe SQL Execution (supabase/supabase, 111k stars) and Citus Backport (citusdata/citus, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bump Up Ducklake?
relytcloud (a GitHub organization) maintains it in relytcloud/pg_ducklake, which has 143 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.
Source: relytcloud/pg_ducklake on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.