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.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/clickhousectl-cloud-deploy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The skill body is a well-sequenced, highly actionable deployment workflow with concrete commands, validation checkpoints, and complete connection examples. Its main weaknesses are mild redundancy with the frontmatter and the lack of an explicit error-recovery feedback loop.

Suggestions

Remove or shrink the 'When to Apply' section since it duplicates the frontmatter description, reclaiming tokens without losing trigger guidance.

Add an explicit feedback loop for the readiness check (e.g., poll 'cloud service get' until state is 'running', with a retry on failure) to lift workflow clarity toward the top anchor.

Consider moving the three language-specific connection snippets into a references file and linking to it, so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands and concrete steps, but the 'When to Apply' section duplicates the frontmatter triggers and the sign-up pitch is somewhat padded, so it is not the lean anchor-5 case.

4 / 5

Actionability

Fully executable guidance throughout — concrete shell commands (login, service create/get, service client) and complete copy-paste-ready connection code in Python, Node, and Go cover the common cases with only appropriate placeholders.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints (verify auth via 'cloud org list', wait for service ready via state check, verify tables via SHOW TABLES/DESCRIBE) and destructive-op auth gating; the gap is the absence of an explicit error-recovery feedback loop, keeping it below anchor 5.

4 / 5

Progressive Disclosure

Well-organized with clearly headed steps and no broken or nested references (no bundle files exist); all content is inline, which is reasonable at 230 lines though the multi-language connection examples could arguably be externalized.

4 / 5

Total

17

/

20

Passed

Description

75%Weight 40%Scale 1-5

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

The description is strong, leading with an explicit 'Use when' clause and several concrete, natural trigger phrases tied to a clear ClickHouse Cloud niche. Its main limitation is that the listed actions overlap as synonyms and the 'what' is folded into the 'when' list rather than stated separately.

Suggestions

Lead with a concise declarative 'what' statement (e.g., 'Deploys and migrates ClickHouse to ClickHouse Cloud via clickhousectl.') before the 'Use when' trigger list to fully separate what from when.

Diversify the action list beyond synonyms (deploy/host/use are largely the same) by adding distinct operations like 'create a cloud service', 'authenticate the CLI', or 'migrate local schemas' to improve specificity and trigger coverage.

DimensionReasoningScore

Specificity

Lists several specific actions ('deploy ClickHouse to the cloud', 'host a managed ClickHouse service', 'migrate from a local ClickHouse setup to ClickHouse Cloud'), but several entries are near-synonyms rather than distinct operations, leaving minor coverage gaps.

4 / 5

Completeness

An explicit 'Use when a user wants to ...' clause answers 'when' with five concrete triggers, and the 'what' (deploy to ClickHouse Cloud) is present but embedded as the first intent rather than a standalone declarative sentence, matching the anchor-4 example.

4 / 5

Trigger Term Quality

Natural phrases a user would say ('deploy ClickHouse to the cloud', 'go to production', 'migrate ... to ClickHouse Cloud') are present, but some synonyms and variations are missing, so it is not the comprehensive anchor-5 case.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (ClickHouse Cloud deploy/migrate) with distinct triggers, with only minor overlap risk against closely related skills such as the referenced local-dev skill.

4 / 5

Total

16

/

20

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.