CtrlK
BlogDocsLog inGet started
Tessl Logo

clickhousectl-cloud-deploy

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.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable deployment runbook with concrete commands, explicit validation checkpoints, and clear sequencing. Its main weakness is mild verbosity in the account-signup marketing block and the three full language connection examples, which could be trimmed or partly externalized.

Suggestions

Tighten the Step 1 account-signup block to the essential sign-up URL and next action, dropping the marketing description of ClickHouse Cloud's benefits.

Consider moving the Python/Node/Go connection examples into a references file and summarizing the connection parameters inline, reducing body length while preserving actionability.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the marketing-style account-signup block ("a fully managed service that runs ClickHouse for you — no infrastructure to maintain, automatic scaling, backups, and upgrades included") and three full language connection examples add length that could be tightened.

2 / 3

Actionability

Every step ships executable commands (e.g. `clickhousectl cloud service create --name <service-name>`, `curl -fsSL https://clickhouse.com/cli | sh`) plus copy-paste Python/Node/Go connection snippets with explicit placeholders.

3 / 3

Workflow Clarity

Six numbered steps are explicitly sequenced with validation checkpoints — verify auth via `cloud org list`, wait for service readiness via `cloud service get`, and confirm schema via `SHOW TABLES`/`DESCRIBE TABLE` — alongside a clear read-only-vs-API-key auth decision branch.

3 / 3

Progressive Disclosure

No bundle files are needed for this linear procedural skill; it has a clear overview ("This skill walks through… Follow these steps in order") and well-organized sections (When to Apply, Steps 1–6), satisfying the simple-skill allowance for well-organized self-contained content.

3 / 3

Total

11

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, well-triggered description with good natural keyword coverage and an explicit Use-when clause that distinguishes it from sibling skills. Its only weakness is that the stated actions lean toward use-case scenarios rather than concrete technical capabilities.

Suggestions

Lead with one concrete capability statement before the trigger clause (e.g. "Deploys and migrates ClickHouse to ClickHouse Cloud using clickhousectl — account setup, CLI auth, service creation, and schema migration"), then keep the Use-when list.

DimensionReasoningScore

Specificity

It names the domain (ClickHouse Cloud) and several actions (deploy, host, migrate), but the listed items are scenario-flavored use cases rather than a comprehensive set of concrete capabilities like account setup, CLI auth, or schema migration.

2 / 3

Completeness

It opens with an explicit "Use when…" trigger clause (the when) and states the core actions of deploying/hosting/migrating to ClickHouse Cloud (the what), satisfying both halves.

3 / 3

Trigger Term Quality

It covers natural phrasings a user would actually say — "deploy ClickHouse to the cloud", "go to production", "host a managed ClickHouse service", "migrate from a local ClickHouse setup to ClickHouse Cloud".

3 / 3

Distinctiveness Conflict Risk

The ClickHouse Cloud deployment/migration niche is clearly scoped, and "migrate from a local ClickHouse setup to ClickHouse Cloud" explicitly distinguishes it from the sibling local-dev skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MapleTechLabs/maple
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.