Clickhouse Cloud Management
CheckedAutomates ClickHouse Cloud cluster provisioning, scaling, monitoring, and optimization via Terrylica's intelligent AI agent.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add terrylica/cc-skills --skill clickhouse-cloud-management -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
terrylica
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned terrylica/cc-skills at 3a1dc29965.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3a1dc29965
- Scanned
- 3 files, 423 lines
About this skill
What it does
This skill automates ClickHouse Cloud user and permission management using SQL commands sent over an HTTP interface. It allows AI agents to create database users, grant or revoke permissions (GRANT/REVOKE), and troubleshoot authentication issues within a ClickHouse Cloud environment. Crucially, this skill manages database users – distinct from API keys which manage the ClickHouse Cloud management API.
When to use it
This skill is useful in these scenarios:
- Creating new database users for your ClickHouse Cloud instances.
- Managing user permissions within ClickHouse databases (granting or revoking access).
- Testing connectivity to your ClickHouse Cloud environment.
- Diagnosing and resolving authentication problems.
- Understanding the difference between API keys and database users in ClickHouse Cloud.
Key capabilities
- User Creation: Creates new database users using
CREATE USERSQL commands. - Permission Management: Grants and revokes permissions on databases and tables using
GRANTandREVOKESQL commands. - User Deletion: Removes existing database users with the
DROP USERcommand. - HTTP Interface Interaction: Communicates with ClickHouse Cloud exclusively via an HTTP interface (port 443, HTTPS).
Example prompts
Here are some example prompts you can use:
- "Create a new ClickHouse user named 'my_reader' with a strong password."
- "Grant SELECT permissions on the 'deribit.*' database to the user 'my_reader'."
- "Delete the user 'my_reader' from ClickHouse Cloud."
Tips & gotchas
- Password Requirements: ClickHouse Cloud enforces strict password policies: minimum 12 characters, at least one uppercase letter, and at least one special character.
- API Key vs. Database User: Remember this skill manages database users for authenticating to ClickHouse itself; API keys are used for the management console.
- HTTP Only: ClickHouse Cloud only exposes an HTTP interface publicly. Native protocol access requires AWS PrivateLink and enterprise setup.