[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWCSXM0ZW2VRWMRK2TWK3W":3,"skill-same:01M7BWCSXM0ZW2VRWMRK2TWK3W":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BWCSXM0ZW2VRWMRK2TWK3W","clickhousectl-cloud-deploy",null,"Use when a user wants to deploy ClickHouse to the cloud, go to production, use ClickHouse Cloud, host a managed ClickHouse service, or migrate from a local ClickHouse setup to ClickHouse Cloud.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fclickhouse-agent-skills\u002Fclickhousectl-cloud-deploy\u002Fskills\u002Fclickhousectl-cloud-deploy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clickhousectl-cloud-deploy\ndescription: Use when a user wants to deploy ClickHouse to the cloud, go to production, use ClickHouse Cloud, host a managed ClickHouse service, or migrate from a local ClickHouse setup to ClickHouse Cloud.\nlicense: Apache-2.0\nmetadata:\n  author: ClickHouse Inc\n  version: \"0.2.0\"\n---\n\n# Deploy to ClickHouse Cloud\n\nThis skill walks through deploying to ClickHouse Cloud using `clickhousectl`. It covers account setup, CLI authentication, service creation, schema migration, and connecting your application. Follow these steps in order.\n\n## When to Apply\n\nUse this skill when the user wants to:\n- Deploy their ClickHouse application to production\n- Host ClickHouse as a managed cloud service\n- Migrate from a local ClickHouse setup to ClickHouse Cloud\n- Create a ClickHouse Cloud service\n- Set up ClickHouse Cloud for the first time\n\n---\n\n## Step 1: Sign up for ClickHouse Cloud\n\nBefore using any cloud commands, the user needs a ClickHouse Cloud account.\n\n**Ask the user:** \"Do you already have a ClickHouse Cloud account?\"\n\n**If they do not have an account**, explain:\n\n> ClickHouse Cloud is a fully managed service that runs ClickHouse for you — no infrastructure to maintain, automatic scaling, backups, and upgrades included. There's a free trial so you can get started without a credit card.\n>\n> To create an account, go to: **https:\u002F\u002Fclickhouse.cloud**\n>\n> Sign up with your email, Google, or GitHub account. Once you're in the console, let me know and we'll continue with the next step.\n\n**Wait for the user to confirm** they have signed up or already have an account before proceeding.\n\n---\n\n## Step 2: Authenticate the CLI\n\nFirst, ensure `clickhousectl` is installed. Check with:\n\n```bash\nwhich clickhousectl\n```\n\nIf not found, install it:\n\n```bash\ncurl -fsSL https:\u002F\u002Fclickhouse.com\u002Fcli | sh\n```\n\nAuthenticate `clickhousectl` with a ClickHouse Cloud API key.\n\n### Create an API key\n\nGuide the user through creating one in the ClickHouse Cloud console:\n\n> 1. Click the **gear icon** (Settings) in the left sidebar\n> 2. Go to **API Keys**\n> 3. Click **Create API Key**\n> 4. Give it a name (e.g., \"clickhousectl\")\n> 5. Select the **Admin** role for the key. Admin is needed because `cloud service query` auto-provisions a per-service query endpoint API key on first use, which requires permission to create keys. Developer-scoped keys can manage services but may not be able to complete the auto-provisioning step.\n> 6. Click **Generate API Key**\n> 7. **Copy both the Key ID and the Key Secret** — the secret is only shown once\n\n### Authenticate clickhousectl with the key\n\nAsk the user to **open a new terminal tab in the same working directory** and run the login command there with their Key ID and Secret — this keeps the secret out of the chat session. Tell them to come back and let you know once it's done.\n\n```bash\nclickhousectl cloud login --api-key \u003Ckey> --api-secret \u003Csecret>\n```\n\nBoth `--api-key` and `--api-secret` are required — if the user only has one, tell them both are needed.\n\n---\n\n**To verify authentication works:**\n\n```bash\nclickhousectl cloud org list\n```\n\nThis should return the user's organization.\n\n---\n\n## Step 3: Create a cloud service\n\nCreate a new ClickHouse Cloud service:\n\n```bash\nclickhousectl cloud service create --name \u003Cservice-name>\n```\n\nFrom the output, add the HTTPS host and port to `.env` as `CLICKHOUSE_HOST` and `CLICKHOUSE_PORT`. Make sure `.env` is gitignored.\n\nThen poll until the service state is `running`:\n\n```bash\nclickhousectl cloud service get \u003Cservice-id>\n```\n\n---\n\n## Step 4: Migrate schemas\n\nIf the user has local table definitions (e.g., from using the `clickhousectl-local-dev` skill), migrate them to the cloud service.\n\nUse `cloud service query` to run SQL against the cloud service over HTTP. Just pass the service name (or `--id`).\n\n**Read the local schema files** from `clickhouse\u002Ftables\u002F` and apply each one to the cloud service:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> \\\n  --queries-file clickhouse\u002Ftables\u002F\u003Ctable>.sql\n```\n\nApply them in dependency order — tables referenced by materialized views should be created first.\n\n**Also apply materialized views** if they exist:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> \\\n  --queries-file clickhouse\u002Fmaterialized_views\u002F\u003Cview>.sql\n```\n\nTo target a specific database, pass `--database \u003Cname>`.\n\n---\n\n## Step 5: Verify the deployment\n\nConnect to the cloud service and confirm tables exist:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \"SHOW TABLES\"\n```\n\nRun a test query to confirm the schema is correct:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \"DESCRIBE TABLE \u003Ctable-name>\"\n```\n\n---\n\n## Step 6: Create a dedicated user for the application\n\nThe `default` user has full admin rights and should not be used by the application. Create a dedicated user scoped to the schema deployed in Step 4.\n\nGenerate a strong random password and append the credentials to `.env` **before** creating the user, so the password is persisted even if a subsequent step fails:\n\n```bash\nPASSWORD=$(openssl rand -base64 32)\necho \"CLICKHOUSE_USER=app_user\" >> .env\necho \"CLICKHOUSE_PASSWORD=$PASSWORD\" >> .env\n```\n\nThen create the user and grant the minimum permissions the app needs. Replace `\u003Cdatabase>` with the database the schema lives in (often `default`):\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \\\n  \"CREATE USER app_user IDENTIFIED BY '$PASSWORD'\"\n\nclickhousectl cloud service query --name \u003Cservice-name> --query \\\n  \"GRANT SELECT, INSERT ON \u003Cdatabase>.* TO app_user\"\n```\n\nAdjust the grants to fit the app:\n\n- Read-only app → drop `INSERT`\n- Needs to create\u002Fdrop its own tables → also grant `CREATE TABLE, DROP TABLE` on the database (but prefer running migrations as the admin user instead)\n- Multiple databases → repeat the `GRANT` per database, or scope per table with `ON \u003Cdatabase>.\u003Ctable>`\n\nVerify the user exists and has the expected grants:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \"SHOW GRANTS FOR app_user\"\n```\n\nClickHouse cannot reveal the password later, so if `.env` is lost, the user must reset the password via `ALTER USER app_user IDENTIFIED BY '\u003Cnew>'`.\n\n---\n\nThe application can now use the credentials in `.env` to connect to ClickHouse Cloud.","# Deploy to ClickHouse Cloud\n\nThis skill walks through deploying to ClickHouse Cloud using `clickhousectl`. It covers account setup, CLI authentication, service creation, schema migration, and connecting your application. Follow these steps in order.\n\n## When to Apply\n\nUse this skill when the user wants to:\n- Deploy their ClickHouse application to production\n- Host ClickHouse as a managed cloud service\n- Migrate from a local ClickHouse setup to ClickHouse Cloud\n- Create a ClickHouse Cloud service\n- Set up ClickHouse Cloud for the first time\n\n---\n\n## Step 1: Sign up for ClickHouse Cloud\n\nBefore using any cloud commands, the user needs a ClickHouse Cloud account.\n\n**Ask the user:** \"Do you already have a ClickHouse Cloud account?\"\n\n**If they do not have an account**, explain:\n\n> ClickHouse Cloud is a fully managed service that runs ClickHouse for you — no infrastructure to maintain, automatic scaling, backups, and upgrades included. There's a free trial so you can get started without a credit card.\n>\n> To create an account, go to: **https:\u002F\u002Fclickhouse.cloud**\n>\n> Sign up with your email, Google, or GitHub account. Once you're in the console, let me know and we'll continue with the next step.\n\n**Wait for the user to confirm** they have signed up or already have an account before proceeding.\n\n---\n\n## Step 2: Authenticate the CLI\n\nFirst, ensure `clickhousectl` is installed. Check with:\n\n```bash\nwhich clickhousectl\n```\n\nIf not found, install it:\n\n```bash\ncurl -fsSL https:\u002F\u002Fclickhouse.com\u002Fcli | sh\n```\n\nAuthenticate `clickhousectl` with a ClickHouse Cloud API key.\n\n### Create an API key\n\nGuide the user through creating one in the ClickHouse Cloud console:\n\n> 1. Click the **gear icon** (Settings) in the left sidebar\n> 2. Go to **API Keys**\n> 3. Click **Create API Key**\n> 4. Give it a name (e.g., \"clickhousectl\")\n> 5. Select the **Admin** role for the key. Admin is needed because `cloud service query` auto-provisions a per-service query endpoint API key on first use, which requires permission to create keys. Developer-scoped keys can manage services but may not be able to complete the auto-provisioning step.\n> 6. Click **Generate API Key**\n> 7. **Copy both the Key ID and the Key Secret** — the secret is only shown once\n\n### Authenticate clickhousectl with the key\n\nAsk the user to **open a new terminal tab in the same working directory** and run the login command there with their Key ID and Secret — this keeps the secret out of the chat session. Tell them to come back and let you know once it's done.\n\n```bash\nclickhousectl cloud login --api-key \u003Ckey> --api-secret \u003Csecret>\n```\n\nBoth `--api-key` and `--api-secret` are required — if the user only has one, tell them both are needed.\n\n---\n\n**To verify authentication works:**\n\n```bash\nclickhousectl cloud org list\n```\n\nThis should return the user's organization.\n\n---\n\n## Step 3: Create a cloud service\n\nCreate a new ClickHouse Cloud service:\n\n```bash\nclickhousectl cloud service create --name \u003Cservice-name>\n```\n\nFrom the output, add the HTTPS host and port to `.env` as `CLICKHOUSE_HOST` and `CLICKHOUSE_PORT`. Make sure `.env` is gitignored.\n\nThen poll until the service state is `running`:\n\n```bash\nclickhousectl cloud service get \u003Cservice-id>\n```\n\n---\n\n## Step 4: Migrate schemas\n\nIf the user has local table definitions (e.g., from using the `clickhousectl-local-dev` skill), migrate them to the cloud service.\n\nUse `cloud service query` to run SQL against the cloud service over HTTP. Just pass the service name (or `--id`).\n\n**Read the local schema files** from `clickhouse\u002Ftables\u002F` and apply each one to the cloud service:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> \\\n  --queries-file clickhouse\u002Ftables\u002F\u003Ctable>.sql\n```\n\nApply them in dependency order — tables referenced by materialized views should be created first.\n\n**Also apply materialized views** if they exist:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> \\\n  --queries-file clickhouse\u002Fmaterialized_views\u002F\u003Cview>.sql\n```\n\nTo target a specific database, pass `--database \u003Cname>`.\n\n---\n\n## Step 5: Verify the deployment\n\nConnect to the cloud service and confirm tables exist:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \"SHOW TABLES\"\n```\n\nRun a test query to confirm the schema is correct:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \"DESCRIBE TABLE \u003Ctable-name>\"\n```\n\n---\n\n## Step 6: Create a dedicated user for the application\n\nThe `default` user has full admin rights and should not be used by the application. Create a dedicated user scoped to the schema deployed in Step 4.\n\nGenerate a strong random password and append the credentials to `.env` **before** creating the user, so the password is persisted even if a subsequent step fails:\n\n```bash\nPASSWORD=$(openssl rand -base64 32)\necho \"CLICKHOUSE_USER=app_user\" >> .env\necho \"CLICKHOUSE_PASSWORD=$PASSWORD\" >> .env\n```\n\nThen create the user and grant the minimum permissions the app needs. Replace `\u003Cdatabase>` with the database the schema lives in (often `default`):\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \\\n  \"CREATE USER app_user IDENTIFIED BY '$PASSWORD'\"\n\nclickhousectl cloud service query --name \u003Cservice-name> --query \\\n  \"GRANT SELECT, INSERT ON \u003Cdatabase>.* TO app_user\"\n```\n\nAdjust the grants to fit the app:\n\n- Read-only app → drop `INSERT`\n- Needs to create\u002Fdrop its own tables → also grant `CREATE TABLE, DROP TABLE` on the database (but prefer running migrations as the admin user instead)\n- Multiple databases → repeat the `GRANT` per database, or scope per table with `ON \u003Cdatabase>.\u003Ctable>`\n\nVerify the user exists and has the expected grants:\n\n```bash\nclickhousectl cloud service query --name \u003Cservice-name> --query \"SHOW GRANTS FOR app_user\"\n```\n\nClickHouse cannot reveal the password later, so if `.env` is lost, the user must reset the password via `ALTER USER app_user IDENTIFIED BY '\u003Cnew>'`.\n\n---\n\nThe application can now use the credentials in `.env` to connect to ClickHouse Cloud.",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"ClickHouse Inc","0.2.0","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fclickhouse-agent-skills\u002Fclickhousectl-cloud-deploy\u002Fskills\u002Fclickhousectl-cloud-deploy",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill clickhousectl-cloud-deploy",{"tool":41,"command":42},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill clickhousectl-cloud-deploy",{"tool":44,"command":45},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill clickhousectl-cloud-deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fclickhouse-agent-skills\u002Fclickhousectl-cloud-deploy\u002Fskills\u002Fclickhousectl-cloud-deploy\u002FSKILL.md",true,[],[50,58,63,70,75,82],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":83,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]