clickhouse-cloud-management — Claude Code skill: setup guide
clickhouse-cloud-management manages ClickHouse Cloud database users and access permissions using SQL statements over HTTPS.
MIT 126 installs ★ 3 updated 2026-10-25
npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a claude-codeWhat clickhouse-cloud-management does
This skill handles database user administration for ClickHouse Cloud directly from the terminal. It issues SQL commands like CREATE USER, GRANT, and DROP USER via curl payloads directed at the cluster HTTPS endpoint.
Public ClickHouse Cloud endpoints accept traffic only on port 443 over HTTP, meaning the native wire protocol is inaccessible without AWS PrivateLink. Passwords must be at least 12 characters long and include an uppercase letter plus a special character, or the cloud instance rejects the command.
What it helps with
- create a read-only database user for analytics
- grant database permissions via SQL over the HTTP interface
- verify cluster reachability with a test query
- remove unused ClickHouse database accounts
Example prompts for the agent
- Create a read-only user for the deribit database in ClickHouse Cloud
- Test connectivity to my ClickHouse Cloud instance with SELECT 1
- Grant SELECT and INSERT permissions on mydb to app_user
How to install clickhouse-cloud-management
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a claude-code2Manually: put the files in place
~/.claude/skills/clickhouse-cloud-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/clickhouse-cloud-management/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a codex2Manually: put the files in place
.agents/skills/clickhouse-cloud-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a cursor2Manually: put the files in place
.cursor/skills/clickhouse-cloud-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install terrylica/cc-skills plugins/devops-tools/skills/clickhouse-cloud-management2Manually: put the files in place
.github/skills/clickhouse-cloud-management/SKILL.md1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/terrylica/cc-skills --path plugins/devops-tools/skills/clickhouse-cloud-managementManually: put the files in place
.devin/skills/clickhouse-cloud-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about clickhouse-cloud-management
How do I install clickhouse-cloud-management in Claude Code?
Run npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a claude-code.
What does the clickhouse-cloud-management skill do?
It guides the agent through managing database users, privileges, and connection diagnostics in ClickHouse Cloud over the HTTPS interface.
Why does the skill use HTTP curl commands instead of native ports?
ClickHouse Cloud exposes only port 443 to the public internet. Connecting over the native protocol on port 9440 requires an enterprise AWS PrivateLink setup.
Source text
SKILL.md · MIT
--- name: clickhouse-cloud-management description: ClickHouse Cloud user and permission management. TRIGGERS - create ClickHouse user, ClickHouse permissions, ClickHouse Cloud credentials. allowed-tools: Read, Bash --- # ClickHouse Cloud Management ADR: 2025-12-08-clickhouse-cloud-management-skill > **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues. ## Overview ClickHouse Cloud user and permission management via SQL commands over HTTP interface. This skill covers database user creation, permission grants, and credential management for ClickHouse Cloud instances. **Schema documentation principle**: All ClickHouse table/column COMMENTs are the single source of truth (SSoT). When creating tables or columns, always include COMMENT clauses. See `quality-tools:clickhouse-architect` for the full COMMENT SSoT policy. ## When to Use This Skill Invoke this skill when: - Creating database users for ClickHouse Cloud - Managing user permissions (GRANT/REVOKE) - Testing ClickHouse Cloud connectivity - Troubleshooting authentication issues - Understanding API key vs database user distinction ## Key Concepts ### Management Options ClickHouse Cloud provides two management interfaces with different capabilities: | Task | Via SQL (CLI/HTTP) | Via Cloud Console | | -------------------- | ------------------ | ----------------- | | Create database user | CREATE USER | Supported | | Grant permissions | GRANT | Supported | | Delete user | DROP USER | Supported | | Create API key | Not possible | Only here | **Key distinction**: Database users (created via SQL) authenticate to ClickHouse itself. API keys (created via console) authenticate to the ClickHouse Cloud management API. ### Connection Details ClickHouse Cloud exposes only HTTP interface publicly: - **Port**: 443 (HTTPS) - **Protocol**: HTTP (not native ClickHouse protocol) - **Native protocol**: Requires AWS PrivateLink (not available without enterprise setup) ### Password Requirements ClickHouse Cloud enforces strong password policy: - Minimum 12 characters - At least 1 uppercase letter - At least 1 special character Example compliant password: `StrongPass@2025!` ## Quick Reference ### Create Read-Only User ```bash curl -s "https://default:PASSWORD@HOST:443/" --data-binary \ "CREATE USER my_reader IDENTIFIED BY 'StrongPass@2025!' SETTINGS readonly = 1" ``` ### Grant Database Access ```bash curl -s "https://default:PASSWORD@HOST:443/" --data-binary \ "GRANT SELECT ON deribit.* TO my_reader" ``` ### Delete User ```bash curl -s "https://default:PASSWORD@HOST:443/" --data-binary \ "DROP USER my_reader" ``` For comprehensive SQL patterns and advanced permission scenarios, see [SQL Patterns Reference](./references/sql-patterns.md). ## Credential Sources ### 1Password Items (Engineering Vault) | Item | Purpose | | ------------------------------------------------ | ----------------------------------------- | | ClickHouse Cloud - API Key (Admin) | Cloud management API (console operations) | | ClickHouse Cloud - API Key (Developer Read-only) | Cloud management API (read-only) | | gapless-deribit-clickhouse | Database `default` user credentials | ### Retrieving Credentials ```bash # Database credentials (for SQL commands) op item get "gapless-deribit-clickhouse" --vault Engineering --reveal # API key (for cloud management API) op item get "ClickHouse Cloud - API Key (Admin)" --vault Engineering --reveal ``` ## Common Workflows ### Workflow 1: Create Application User 1. Retrieve `default` user credentials from 1Password 2. Create new user with appropriate permissions: ```bash HOST="your-instance.clickhouse.cloud" PASSWORD="default-user-password" # Create user curl -s "https://default:$PASSWORD@$HOST:443/" --data-binary \ "CREATE USER app_user IDENTIFIED BY 'AppPass@2025!'" # Grant specific database access curl -s "https://default:$PASSWORD@$HOST:443/" --data-binary \ "GRANT SELECT, INSERT ON mydb.* TO app_user" ``` ### Workflow 2: Verify User Exists ```bash curl -s "https://default:$PASSWORD@$HOST:443/" --data-binary "SHOW USERS" ``` ### Workflow 3: Test Connection ```bash curl -s "https://user:password@HOST:443/" --data-binary "SELECT 1" ``` Expected output: `1` (single row with value 1) ## Troubleshooting ### Authentication Failed - Verify password meets complexity requirements - Check host URL includes port 443 - Ensure using HTTPS (not HTTP) ### Permission Denied - Verify user has required GRANT statements - Check database and table names are correct - Confirm user was created with correct settings ### Connection Timeout - ClickHouse Cloud only exposes port 443 publicly - Native protocol (port 9440) requires PrivateLink - Use HTTP interface with curl or clickhouse-client HTTP mode ## Next Steps After User Creation <!-- ADR: 2025-12-10-clickhouse-skill-delegation --> After creating a ClickHouse user, invoke **`devops-tools:clickhouse-pydantic-config`** to generate DBeaver configuration with the new credentials. ## Additional Resources ### Reference Files For detailed patterns and advanced techniques, consult: - **[references/sql-patterns.md](./references/sql-patterns.md)** - Complete SQL syntax reference with examples ## Python Driver Policy For Python application code connecting to ClickHouse Cloud, use `clickhouse-connect` (official HTTP driver). See [`clickhouse-architect`](../../../quality-tools/skills/clickhouse-architect/SKILL.md#python-driver-policy) for recommended code patterns and why to avoid `clickhouse-driver` (community). ## Related Skills - `quality-tools:clickhouse-architect` - Schema design, compression codecs, Python driver policy - `devops-tools:clickhouse-pydantic-config` - DBeaver configuration generation - `devops-tools:doppler-secret-validation` - For storing credentials in Doppler - `devops-tools:doppler-workflows` - For credential rotation workflows ## Post-Execution Reflection After this skill completes, check before closing: 1. **Did the command succeed?** — If not, fix the instruction or error table that caused the failure. 2. **Did parameters or output change?** — If the underlying tool's interface drifted, update Usage examples and Parameters table to match. 3. **Was a workaround needed?** — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround. Only update if the issue is real and reproducible — not speculative.
© terrylica · MIT · terrylica/cc-skills