Agent skill

Version Upgrade Advisor

by chmonitor in chmonitor/chmonitor

Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist.

GPL-3.0Auto-check passedDatabases

Install Version Upgrade Advisor

skills CLI
$ npx skills add chmonitor/chmonitor --skill version-upgrade-advisor -a claude-code

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

GitHub CLI
$ gh skill install chmonitor/chmonitor version-upgrade-advisor --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/chmonitor/chmonitor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/version-upgrade-advisor .claude/skills/version-upgrade-advisor && 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/

Facts

Skill name
version-upgrade-advisor
GitHub stars
298
Token cost
~1.6k tokens
SKILL.md length
620 words
Files
1
Skills in repo
53
Repo updated
First seen
Licence
GPL-3.0

At a glance

Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist.

  • Works in 6 steps: One significant line at a time — do not… → Read the changelog first — ClickHouse… → Test on staging with production data… → …
  • Tasks that involve Data warehousing
  • SKILL.md covers Detect Current Version and…, How ClickHouse Versioning Works, General Upgrade Guidance and What You Typically Gain by…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Version Upgrade Advisor is an agent skill from chmonitor/chmonitor. Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist.

Its SKILL.md is about 1.6k 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, Code migrations and Changelog and release notes. It works with ClickHouse. The repository describes itself as: Open-source operational advisor for ClickHouse — real-time monitoring plus AI-driven index/partition/materialized-view recommendations. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Data warehousing
  • Tasks that involve Code migrations
  • Tasks that involve Changelog and release notes

Example prompts

  • “Use the version-upgrade-advisor skill to advise whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain…”
  • “/version-upgrade-advisor”

Workflow steps

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

  1. One significant line at a time — do not skip multiple major version lines (e.g. 23.3 → 24.3 → 25.3, not 23.3 → 25.3 in one hop). Review…
  2. Read the changelog first — ClickHouse marks breaking changes explicitly. Settings that change defaults or are removed are the most common…
  3. Test on staging with production data volumes — especially joins, aggregations with large state, and any experimental features you use.
  4. Back up before upgrading — at minimum export table schemas; ideally snapshot data or use replicas as rollback points.
  5. Rolling upgrade for replicated clusters — upgrade one replica at a time. ClickHouse supports mixed-version replication within the same…
  6. Upgrade ClickHouse Keeper / ZooKeeper in sync — if using Keeper, check compatibility requirements for the version pair.

What it can do on your machine

Read from SKILL.md and the folder at commit fc39ef0. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are sql).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Version Upgrade Advisor loads about 1.6k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 620 words of instructions outside code blocks.

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

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

The full file from chmonitor/chmonitor at commit fc39ef0, republished under its GPL-3.0 licence (© chmonitor). 620 words, ~1,643 tokens.

Download SKILL.mdSave it as .claude/skills/version-upgrade-advisor/SKILL.md (or your agent's skills folder).
name
version-upgrade-advisor
description
Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist.

Version Upgrade Advisor

Accuracy note: This skill covers method, not memorized changelogs. For exact per-version details — new functions, removed settings, default-value changes — always consult the official ClickHouse release notes at clickhouse.com/docs/whats-new/changelog. Never assert specific changelog facts without directing the user to verify them.

Detect Current Version and Uptime

sql
SELECT version(), uptime();

The get_metrics tool also returns the server version in its output — check there first before running a query.

Key things to capture before advising:

  • Current version string (e.g. 24.3.5.46)
  • Uptime (a long uptime on an old version is a signal the operator avoids upgrades — note this)
  • Whether this is a cluster: SELECT * FROM system.clusters — mixed versions across replicas matter

How ClickHouse Versioning Works

Format: YY.M.patch.build — e.g. 24.3.5.46 = year 2024, month 3, patch 5.

Release types:

  • Regular releases — monthly, supported until the next regular release (~1 month). Good for tracking latest features; require frequent upgrades.
  • LTS releases — designated every ~6 months (historically .3 and .8 months); receive backported fixes for ~1 year. The repo's schema matrix (see docs/clickhouse-schemas/index.md) covers: 23.3, 23.8, 24.3, 24.8 as LTS anchors.

Support window: LTS releases get security/critical backports for roughly 1 year after release. Regular releases get fixes only until the next release. Running a version past its support window means no patches — upgrade recommended.

Guidance: prefer upgrading to the latest LTS if stability matters; track regular releases only if you need cutting-edge features and can upgrade frequently.

General Upgrade Guidance

  1. One significant line at a time — do not skip multiple major version lines (e.g. 23.3 → 24.3 → 25.3, not 23.3 → 25.3 in one hop). Review the backward-incompatible changes for each intermediate LTS.
  2. Read the changelog first — ClickHouse marks breaking changes explicitly. Settings that change defaults or are removed are the most common surprises.
  3. Test on staging with production data volumes — especially joins, aggregations with large state, and any experimental features you use.
  4. Back up before upgrading — at minimum export table schemas; ideally snapshot data or use replicas as rollback points.
  5. Rolling upgrade for replicated clusters — upgrade one replica at a time. ClickHouse supports mixed-version replication within the same minor line; check the release notes for the specific hop you are making. Never run permanently mixed-version clusters.
  6. Upgrade ClickHouse Keeper / ZooKeeper in sync — if using Keeper, check compatibility requirements for the version pair.
Show full SKILL.md (240 more words)Show less

What You Typically Gain by Upgrading

These are broad, stable themes — exact improvements vary by version; verify against release notes.

  • Query optimizer improvements — planner rewrites, better join ordering, improved predicate pushdown, new join algorithms (e.g. grace_hash)
  • New functions and data types — aggregate combinators, JSON support expansions, new numeric/date types, string functions
  • Better compression and storage — codec improvements, lighter part metadata, faster merges
  • JOIN performance — hash join improvements, parallel hash, better memory management for large joins
  • Observability — new columns in system.query_log, system.processes, system.errors; better structured logging
  • Security — new auth mechanisms, role/row-level security improvements
  • Async inserts and ingest throughput — deduplication improvements, async insert reliability

Do not cite specific performance numbers or function names without directing the user to verify in the changelog.

Pre-Upgrade Checklist

Before upgrading, audit the following:

sql
-- 1. Check settings that differ from defaults (non-default = potential conflict)
SELECT name, value, default, changed
FROM system.settings
WHERE changed = 1
ORDER BY name;

-- 2. Check for deprecated settings in use
SELECT name, value
FROM system.settings
WHERE name IN (
  -- populate from the target version's deprecation list; do not hard-code here
);

-- 3. List experimental features in use
SELECT name, value
FROM system.settings
WHERE name LIKE '%experimental%' AND value != '0';

-- 4. Check current errors before upgrade (baseline)
SELECT name, value, last_error_message
FROM system.errors
WHERE value > 0
ORDER BY value DESC
LIMIT 20;

-- 5. Verify replication is healthy (replicated clusters only)
SELECT database, table, replica_name, is_leader,
       log_max_index - log_pointer AS lag
FROM system.replicas
WHERE log_max_index - log_pointer > 0
   OR future_parts > 0;

Also check:

  • Any ON CLUSTER DDL in flight — let it finish
  • Active long-running queries — drain or wait
  • Disk space — new versions sometimes need extra space during part rewrite on first startup
  • Whether your client library versions support the new server protocol (especially if upgrading a major line)

Verify After Upgrade

sql
-- Confirm version
SELECT version();

-- Check for new errors since upgrade
SELECT name, value, last_error_message, last_error_time
FROM system.errors
WHERE value > 0
  AND last_error_time > now() - INTERVAL 1 HOUR
ORDER BY value DESC;

-- Confirm replication caught up (clusters)
SELECT database, table, replica_name,
       log_max_index - log_pointer AS lag,
       last_queue_update
FROM system.replicas
ORDER BY lag DESC;

-- Spot-check query performance on known slow queries
-- (run your typical workload; compare system.query_log duration_ms)
SELECT query_id, query, duration_ms
FROM system.query_log
WHERE type = 'QueryFinish'
  AND event_time > now() - INTERVAL 30 MINUTE
ORDER BY duration_ms DESC
LIMIT 20;

Smoke test: run a representative SELECT from each critical table, confirm row counts, verify merges are progressing, check system.merges and system.mutations have no stalled entries.

  • migration-patterns — schema migrations and DDL patterns that may be needed alongside an upgrade
  • clickhouse-best-practices — production settings to review after upgrading (defaults may have changed)
  • hardware-tuning — if upgrading unlocks new compression or parallelism settings, revisit resource tuning

© chmonitor, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/version-upgrade-advisor of chmonitor/chmonitor.

Open the folder on GitHubat commit fc39ef0

Compare with similar skills

Version Upgrade Advisor 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.

Version Upgrade Advisor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Version Upgrade Advisor this skillchmonitor/chmonitor298—~1.6kAutomated safety check: PassGPL-3.0
Chdb SQLvemetric/vemetric3941 repos~1.2kAutomated safety check: PassApache-2.0
Write Doc ExamplesClickHouse/clickhouse-java1.6k—~3.1kAutomated safety check: PassApache-2.0
Clickhouse Architecture Advisorvemetric/vemetric3942 repos~791Automated safety check: PassApache-2.0
Observal AdminObserval/Observal4.1k—~774Automated safety check: PassApache-2.0
ClickHouse RowBinary for Node.jsClickHouse/agent-skills544—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • 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…

    394 GitHub starsUsed in 1 repo~1.2k tokens
    DatabasesAuto-check passed
  • Write Doc Examples

    ClickHouse/clickhouse-java

    Write, rewrite, and format documentation code snippets into reusable, production-ready methods with necessary library imports and clean linting.

    1.6k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs.

    394 GitHub starsUsed in 2 repos~791 tokens
    DatabasesAuto-check passed
  • 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…

    4.1k GitHub stars~774 tokensUpdated today
    DatabasesAuto-check passed
  • ClickHouse RowBinary for Node.js

    ClickHouse/agent-skills

    Generates TypeScript or JavaScript readers and writers for ClickHouse's RowBinary formats over HTTP in Node.js, after checking that RowBinary suits the data.

    544 GitHub stars~1.3k tokensUpdated 8 days ago
    DatabasesAuto-check passed
  • Clickhouse Best Practices

    vemetric/vemetric

    MUST USE when reviewing ClickHouse schemas, queries, or configurations.

    394 GitHub starsUsed in 2 repos~2.6k tokens
    DatabasesAuto-check passed

More from chmonitor/chmonitor

All 53 skills in this repo
  • Hyperframes Creative

    chmonitor/chmonitor

    Non-animation creative direction for HyperFrames videos. An agent skill from chmonitor/chmonitor.

    298 GitHub starsUsed in 5 repos~1.3k tokens
    Auto-check passed
  • Hyperframes Media

    chmonitor/chmonitor

    Audio and media assets for HyperFrames compositions, produced by one shared audio engine (scripts/audio.mjs) — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), background music + sound…

    298 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check: notes
  • Remotion To Hyperframes

    chmonitor/chmonitor

    Port an existing Remotion (React) composition to HyperFrames HTML.

    298 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Music To Video

    chmonitor/chmonitor

    A skill your agent uses when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting.

    298 GitHub starsUsed in 1 repo~4k tokens
    Auto-check: notes
  • Hyperframes Animation

    chmonitor/chmonitor

    All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus…

    298 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • Faceless Explainer

    chmonitor/chmonitor

    turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video, up to ~3 min (sweet spot 30-90s), where every visual is invented (typography, abstract graphics…

    298 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check: notes

Works with

Questions about Version Upgrade Advisor

What does Version Upgrade Advisor do?

Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist. Version Upgrade Advisor is an agent skill from chmonitor/chmonitor. Advises whether and how to upgrade ClickHouse — versioning scheme, upgrade path, what you gain, pre/post-upgrade checklist.

When should I use Version Upgrade Advisor?

Version Upgrade Advisor fits situations like: tasks that involve Data warehousing; tasks that involve Code migrations; tasks that involve Changelog and release notes.

How do I install Version Upgrade Advisor in Claude Code?

Run `npx skills add chmonitor/chmonitor --skill version-upgrade-advisor -a claude-code`. Or copy the skill folder (.agents/skills/version-upgrade-advisor in chmonitor/chmonitor) into .claude/skills/version-upgrade-advisor in your project. Claude Code loads it when a task matches its description.

How do I install Version Upgrade Advisor in Codex?

Run `npx skills add chmonitor/chmonitor --skill version-upgrade-advisor -a codex`. Or copy the skill folder (.agents/skills/version-upgrade-advisor in chmonitor/chmonitor) into .agents/skills/version-upgrade-advisor in your project. Codex loads it when a task matches its description.

Can I use Version Upgrade Advisor 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 chmonitor/chmonitor --skill version-upgrade-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-upgrade-advisor, .gemini/skills/version-upgrade-advisor, .github/skills/version-upgrade-advisor and .opencode/skills/version-upgrade-advisor in your project.

What does Version Upgrade Advisor need to run?

SKILL.md names no scripts, command-line tools or credentials: Version Upgrade Advisor is instructions for the agent only.

Does Version Upgrade Advisor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Version Upgrade Advisor 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 Version Upgrade Advisor use?

Version Upgrade Advisor is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Version Upgrade Advisor use?

About 1.6k tokens (SKILL.md is roughly 6.6k 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 Version Upgrade Advisor?

Skills that share tags, products or a category with Version Upgrade Advisor: Chdb SQL (vemetric/vemetric, 394 stars), Write Doc Examples (ClickHouse/clickhouse-java, 1.6k stars), Clickhouse Architecture Advisor (vemetric/vemetric, 394 stars) and Observal Admin (Observal/Observal, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Upgrade Advisor?

chmonitor (a GitHub organization) maintains it in chmonitor/chmonitor, which has 298 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 5, 2026.

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