Keeper Stress Analysis
ClickHouse/ClickHouse
Analyze ClickHouse Keeper stress-test results from play.clickhouse.com / keeperstresstests data warehouse.
Printing Press CLI for Clickhouse Cloud. An agent skill from mvanhorn/printing-press-library.
$ npx skills add mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clickhouse-cloud --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/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-clickhouse-cloud .claude/skills/pp-clickhouse-cloud && 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 "pp-clickhouse-cloud" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloud into .claude/skills/pp-clickhouse-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clickhouse-cloud", 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/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloudType 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 mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clickhouse-cloud --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-clickhouse-cloud .agents/skills/pp-clickhouse-cloud && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-clickhouse-cloud" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloud into .agents/skills/pp-clickhouse-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clickhouse-cloud", 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 mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clickhouse-cloud --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-clickhouse-cloud .cursor/skills/pp-clickhouse-cloud && 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 "pp-clickhouse-cloud" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloud into .cursor/skills/pp-clickhouse-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clickhouse-cloud", 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/mvanhorn/printing-press-library.git --path cli-skills/pp-clickhouse-cloud--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 mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clickhouse-cloud --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-clickhouse-cloud .gemini/skills/pp-clickhouse-cloud && 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 "pp-clickhouse-cloud" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloud into .gemini/skills/pp-clickhouse-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clickhouse-cloud", 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 mvanhorn/printing-press-library pp-clickhouse-cloudInstalls 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 mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-clickhouse-cloud .github/skills/pp-clickhouse-cloud && 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 "pp-clickhouse-cloud" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloud into .github/skills/pp-clickhouse-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clickhouse-cloud", 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 mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clickhouse-cloud --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-clickhouse-cloud .opencode/skills/pp-clickhouse-cloud && 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 "pp-clickhouse-cloud" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clickhouse-cloud into .opencode/skills/pp-clickhouse-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clickhouse-cloud", 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.
pp-clickhouse-cloudPrinting Press CLI for Clickhouse Cloud. An agent skill from mvanhorn/printing-press-library.
Pp Clickhouse Cloud is an agent skill from mvanhorn/printing-press-library. Printing Press CLI for Clickhouse Cloud.
Its SKILL.md is about 3.9k 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 ClickHouse. The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 76de244. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gonpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
CLICKHOUSE_CLOUD_PASSWORDFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Clickhouse Cloud loads about 3.9k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 1,659 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 noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated 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 mvanhorn/printing-press-library at commit 76de244, republished under its Apache-2.0 licence (© mvanhorn). 1,659 words, ~3,916 tokens.
.claude/skills/pp-clickhouse-cloud/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/cloud/clickhouse-cloud/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the clickhouse-cloud-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install clickhouse-cloud --cli-onlyclickhouse-cloud-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:
go install github.com/mvanhorn/printing-press-library/library/cloud/clickhouse-cloud/cmd/clickhouse-cloud-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
activities — Manage activities
clickhouse-cloud-pp-cli activities activity-get — Returns a single organization activity by ID.clickhouse-cloud-pp-cli activities activity-get-list — Returns a list of all organization activities.byoc-infrastructure — Manage byoc infrastructure
clickhouse-cloud-pp-cli byoc-infrastructure create — Create a new BYOC Infrastructure in the organization. Returns the configuration of the newly created infrastructureclickhouse-cloud-pp-cli byoc-infrastructure delete — Removes a BYOC Infrastructure from the organizationclickhouse-cloud-pp-cli byoc-infrastructure update — Update configuration of the BYOC infrastructure. Returns the modified infrastructureinvitations — Manage invitations
clickhouse-cloud-pp-cli invitations create — Creates organization invitation.clickhouse-cloud-pp-cli invitations delete — Deletes a single organization invitation.clickhouse-cloud-pp-cli invitations get — Returns details for a single organization invitation.clickhouse-cloud-pp-cli invitations get-list — Returns list of all organization invitations.keys — Manage keys
clickhouse-cloud-pp-cli keys openapi-create — Creates new API key.clickhouse-cloud-pp-cli keys openapi-delete — Deletes API key. Only a key not used to authenticate the active request can be deleted.clickhouse-cloud-pp-cli keys openapi-get — Returns a single key details.clickhouse-cloud-pp-cli keys openapi-get-list — Returns a list of all keys in the organization.clickhouse-cloud-pp-cli keys openapi-update — Updates API key properties.members — Manage members
clickhouse-cloud-pp-cli members delete — Removes a user from the organizationclickhouse-cloud-pp-cli members get — Returns a single organization member details.clickhouse-cloud-pp-cli members get-list — Returns a list of all members in the organization.clickhouse-cloud-pp-cli members update — Updates organization member role.organizations — Manage organizations
clickhouse-cloud-pp-cli organizations get — Returns details of a single organization. In order to get the details, the auth key must belong to the organization.clickhouse-cloud-pp-cli organizations get-list — Returns a list with a single organization associated with the API key in the request.clickhouse-cloud-pp-cli organizations update — Updates organization fields. Requires ADMIN auth key role.postgres — Manage postgres
clickhouse-cloud-pp-cli postgres org-prometheus-get — Disclaimer: This beta endpoint is evolving; the API contract may change.clickhouse-cloud-pp-cli postgres service-create — This endpoint is in beta. API contract is stable, and no breaking changes are expected in the future.clickhouse-cloud-pp-cli postgres service-delete — This endpoint is in beta. API contract is stable, and no breaking changes are expected in the future.clickhouse-cloud-pp-cli postgres service-get — This endpoint is in beta. API contract is stable, and no breaking changes are expected in the future.clickhouse-cloud-pp-cli postgres service-get-list — This endpoint is in beta. API contract is stable, and no breaking changes are expected in the future.clickhouse-cloud-pp-cli postgres service-patch — This endpoint is in beta. API contract is stable, and no breaking changes are expected in the future.private-endpoint-config — Manage private endpoint config
clickhouse-cloud-pp-cli private-endpoint-config <organizationId> — Deprecated. Please follow [documentation](https://clickhouse.prometheus — Manage prometheus
clickhouse-cloud-pp-cli prometheus <organizationId> — Returns prometheus metrics for all services in an organization.roles — Manage roles
clickhouse-cloud-pp-cli roles delete — Deletes an existing custom role. System roles cannot be deleted.clickhouse-cloud-pp-cli roles get — Returns details for a specific role.clickhouse-cloud-pp-cli roles get-list — Returns all available roles (system + custom) for an organization.clickhouse-cloud-pp-cli roles patch — Updates an existing custom role. System roles cannot be updated.clickhouse-cloud-pp-cli roles post — Creates a new custom role for an organization with specified policies and actors.services — Manage services
clickhouse-cloud-pp-cli services instance-create — Creates a new service in the organization, and returns the current service state and a password to access the service.clickhouse-cloud-pp-cli services instance-delete — Deletes the service. The service must be in stopped state and is deleted asynchronously after this method call.clickhouse-cloud-pp-cli services instance-get — Returns a service that belongs to the organizationclickhouse-cloud-pp-cli services instance-get-list — Returns a list of all services in the organization.clickhouse-cloud-pp-cli services instance-update — Updates basic service details like service name or IP access list.usage-cost — Manage usage cost
clickhouse-cloud-pp-cli usage-cost <organizationId> — Returns a grand total and a list of dailyWhen you know what you want to do but not which command does it, ask the CLI directly:
clickhouse-cloud-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
Run clickhouse-cloud-pp-cli auth setup to print the URL and steps for getting a key (add --launch to open the URL). Then set:
export CLICKHOUSE_CLOUD_USERNAME="<your-key-id>"
export CLICKHOUSE_CLOUD_PASSWORD="<your-key-secret>"To persist credentials, use clickhouse-cloud-pp-cli auth set-token <key-id> <key-secret>. Stored secrets live in credentials.toml under the data dir, not in config.toml.
Run clickhouse-cloud-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
clickhouse-cloud-pp-cli invitations get mock-value mock-value --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
Agents should treat the CLI's path resolver as part of the runtime contract:
Use --home <dir> for one invocation, or set CLICKHOUSE_CLOUD_HOME=<dir> to relocate all four path kinds under one root.
Use per-kind env vars only when a specific kind must diverge: CLICKHOUSE_CLOUD_CONFIG_DIR, CLICKHOUSE_CLOUD_DATA_DIR, CLICKHOUSE_CLOUD_STATE_DIR, CLICKHOUSE_CLOUD_CACHE_DIR.
Resolution order is per-kind env var, --home, CLICKHOUSE_CLOUD_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.
config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.
Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.
Run clickhouse-cloud-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.
For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:
{
"mcpServers": {
"clickhouse-cloud": {
"command": "clickhouse-cloud-pp-mcp",
"env": {
"CLICKHOUSE_CLOUD_HOME": "/srv/clickhouse-cloud"
}
}
}
}Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use CLICKHOUSE_CLOUD_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing CLICKHOUSE_CLOUD_HOME, or doctor will not find credentials left under the former root.
When you (or the agent) notice something off about this CLI, record it:
clickhouse-cloud-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
clickhouse-cloud-pp-cli feedback --stdin < notes.txt
clickhouse-cloud-pp-cli feedback list --json --limit 10Entries are stored locally as feedback.jsonl under the resolved data dir. They are never POSTed unless CLICKHOUSE_CLOUD_FEEDBACK_ENDPOINT is set AND either --send is passed or CLICKHOUSE_CLOUD_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
clickhouse-cloud-pp-cli profile save briefing --json
clickhouse-cloud-pp-cli --profile briefing invitations get mock-value mock-value
clickhouse-cloud-pp-cli profile list --json
clickhouse-cloud-pp-cli profile show briefing
clickhouse-cloud-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
For endpoints that submit long-running work, the generator detects the submit-then-poll pattern (a job_id/task_id/operation_id field in the response plus a sibling status endpoint) and wires up three extra flags on the submitting command:
| Flag | Purpose |
|---|---|
--wait | Block until the job reaches a terminal status instead of returning the job ID immediately |
--wait-timeout | Maximum wait duration (default 10m, 0 means no timeout) |
--wait-interval | Initial poll interval (default 2s; grows with exponential backoff up to 30s) |
Use async submission without --wait when you want to fire-and-forget; use --wait when you want one command to return the finished artifact.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show clickhouse-cloud-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/cloud/clickhouse-cloud/cmd/clickhouse-cloud-pp-mcp@latestclickhouse-cloud-pp-mcp with your MCP-compatible host using that host's add-server flow.clickhouse-cloud-pp-mcp.which clickhouse-cloud-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:clickhouse-cloud-pp-cli <command> [subcommand] [args] --agentclickhouse-cloud-pp-cli <command> --help.© mvanhorn, 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 cli-skills/pp-clickhouse-cloud of mvanhorn/printing-press-library.
Open the folder on GitHubat commit 76de244
Pp Clickhouse Cloud 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 |
|---|---|---|---|---|---|---|
| Pp Clickhouse Cloud this skillmvanhorn/printing-press-library | 2.1k | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Keeper Stress AnalysisClickHouse/ClickHouse | 50k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 | |
| Perf ComparisonClickHouse/ClickHouse | 50k | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Patch Release CheckClickHouse/ClickHouse | 50k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Clickhouse Architecture Advisorvemetric/vemetric | 395 | 2 repos | ~791 | Automated safety check: Pass | Apache-2.0 | |
| Decompress BinaryClickHouse/ClickHouse | 50k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
ClickHouse/ClickHouse
Analyze ClickHouse Keeper stress-test results from play.clickhouse.com / keeperstresstests data warehouse.
ClickHouse/ClickHouse
Evaluate ClickHouse performance test results from existing CI/dashboard data or local perf.py runs.
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…
vemetric/vemetric
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs.
ClickHouse/ClickHouse
Extract the inner ELF from a ClickHouse self-extracting clickhouse binary, including when its architecture differs from the host (e.g.
ClickHouse/ClickHouse
Show a report of open ClickHouse PRs whose only non-green CI check is "CH Inc sync" (or that are fully green) — i.e.
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Works with
Categories
Printing Press CLI for Clickhouse Cloud. An agent skill from mvanhorn/printing-press-library. Pp Clickhouse Cloud is an agent skill from mvanhorn/printing-press-library. Printing Press CLI for Clickhouse Cloud.
Pp Clickhouse Cloud fits situations like: tasks that involve Data warehousing.
Run `npx skills add mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a claude-code`. Or copy the skill folder (cli-skills/pp-clickhouse-cloud in mvanhorn/printing-press-library) into .claude/skills/pp-clickhouse-cloud in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a codex`. Or copy the skill folder (cli-skills/pp-clickhouse-cloud in mvanhorn/printing-press-library) into .agents/skills/pp-clickhouse-cloud 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 mvanhorn/printing-press-library --skill pp-clickhouse-cloud -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-clickhouse-cloud, .gemini/skills/pp-clickhouse-cloud, .github/skills/pp-clickhouse-cloud and .opencode/skills/pp-clickhouse-cloud in your project.
Going by SKILL.md and its folder, Pp Clickhouse Cloud needs the command-line tools its instructions call (go and npx) and credentials named CLICKHOUSE_CLOUD_PASSWORD. Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, 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 notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Clickhouse Cloud is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k 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 Pp Clickhouse Cloud: 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.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.