clickhousectl-local-dev

Use when a user wants to build an application with ClickHouse, set up a local ClickHouse development environment, install ClickHouse, create a local server, create tables, or start developing with ClickHouse. Covers the full flow from zero to a working local ClickHouse setup.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/clickhousectl-local-dev/SKILL.md

Quality

Content

78%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.

A well-structured, actionable walkthrough with executable commands at every step, a real verification step, and clean single-file organization. The main deductions are small redundancy with the description, a placeholder/typo-level roughness in the commands, and the absence of failure-recovery guidance after schema application.

Suggestions

Fix the typo `.clickhouse/servers/<anem>/data/` (should be `<name>`) and give `<name>` one concrete example value (e.g. `--name dev`) so commands are fully copy-paste runnable.

Add a short failure-recovery note after Step 5/7 (e.g. what to check if `local client` errors or SHOW TABLES returns empty) to close the feedback loop on the database operations.

Trim the "When to Apply" section or the introductory sentence, since both restate the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — no explanations of what ClickHouse is — but the "When to Apply" section largely duplicates the frontmatter description and the opening line "This skill walks through setting up a complete local ClickHouse development environment... Follow these steps in order" is mild padding that could be trimmed.	4 / 5
Actionability	Nearly every step gives a copy-paste-ready command (`curl -fsSL https://clickhouse.com/cli \| sh`, `clickhousectl local install stable`, `clickhousectl local server start --name <name>`) plus complete SQL examples, but `<name>` is never given a concrete example value, Step 5/6 contain comment-only bash blocks, and `.clickhouse/servers/<anem>/data/` contains a typo.	4 / 5
Workflow Clarity	A clearly ordered 7-step sequence with a dedicated verification step (SHOW TABLES, count query) and error recovery in Step 1 (PATH troubleshooting), but there is no guidance on what to do if verification or schema application fails — a feedback-loop gap for database operations that keeps it below the top anchor.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed: the skill is a single well-sectioned walkthrough with clear step headers, and external skill references ("clickhouse-best-practices", "clickhousectl-cloud-deploy") are clearly signaled, conditional, and one level deep.	5 / 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.

A solid, trigger-rich description with explicit "Use when" guidance and mostly concrete actions. It loses points for generic tail phrases ("start developing with ClickHouse"), a scope-flavored rather than direct capability statement, and slight overlap risk with adjacent ClickHouse skills.

Suggestions

Replace the redundant trailing clauses ("start developing with ClickHouse", "Covers the full flow from zero to a working local ClickHouse setup") with a direct capability statement such as "Sets up a local ClickHouse development environment using clickhousectl: installs the binary, starts a local server, and applies table schemas and seed data."

Add natural synonym triggers users might say, e.g. "run ClickHouse locally" or "self-hosted a ClickHouse instance".

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "install ClickHouse", "create a local server", "create tables", "set up a local ClickHouse development environment" — but "build an application with ClickHouse" and "start developing with ClickHouse" are generic, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	The "when" is explicit with multiple concrete triggers ("Use when a user wants to..."), and the "what" is answered by "Covers the full flow from zero to a working local ClickHouse setup" — but the what is stated as scope coverage rather than a direct capability statement, so it falls just below the clearly-explicit-both anchor.	4 / 5
Trigger Term Quality	Good natural-phrase coverage: "install ClickHouse", "set up a local ClickHouse development environment", "create a local server", "create tables" are phrasings users would naturally say, though synonyms like "run ClickHouse locally" or "self-hosted ClickHouse" are missing.	4 / 5
Distinctiveness Conflict Risk	The ClickHouse local-setup niche is well defined with distinct triggers, but "build an application with ClickHouse" is broad and could overlap with general ClickHouse usage or cloud-deployment skills referenced in the body.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MapleTechLabs/maple
Path: .agents/skills/clickhousectl-local-dev/SKILL.md
Commit: 1a03fa7

Reviewed: 11 hours ago

Table of Contents

Discovery Implementation Validation

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.