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

83%

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

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 body is a tight, highly actionable seven-step walkthrough with copy-paste commands and a final verification step. The main improvement is adding intermediate validation checkpoints (validate->fix->retry) for the database operations and fixing the '<anem>' typo.

Suggestions

Add an intermediate checkpoint after Step 4 (e.g. 'clickhousectl local server list' then confirm the named server is running) and a validate->fix->retry note for schema/seed application failures, not just a terminal verify in Step 7.

Fix the typo in Step 4: '.clickhouse/servers/<anem>/data/' should read '<name>'.

Trim or merge the 'When to Apply' list since it largely duplicates the frontmatter description, or repurpose it to surface edge cases not already covered.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept padding (no 'what is ClickHouse' exposition) and each command is followed by a one-line purpose note; not a 5 because the 'When to Apply' list partly echoes the frontmatter description and a few explanatory lines could be trimmed.	4 / 5
Actionability	Every step ships copy-paste-ready commands (e.g. 'clickhousectl local install stable', 'clickhousectl local client --name <name> --queries-file ...') plus complete CREATE TABLE and INSERT examples with concrete version specifiers, covering the common local-dev cases.	5 / 5
Workflow Clarity	Seven steps are clearly ordered and Step 7 supplies a verification checkpoint (SHOW TABLES, SELECT count()) with a Step 1 PATH troubleshooting hint; not a 5 because validation is terminal rather than per-step and there is no explicit validate->fix->retry loop for the database operations.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed steps and the two sibling-skill pointers ('clickhouse-best-practices', 'clickhousectl-cloud-deploy') are one level deep and clearly signaled; not a 5 because it is a single linear file with no content actually split into references, though for this workflow that is reasonable.	4 / 5
	Total	17 / 20 Passed

Description

83%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: it pairs an explicit 'Use when' trigger with concrete, natural-sounding actions and a clear local-ClickHouse niche. Minor gains are available from adding synonyms and sharper distinction from sibling ClickHouse skills.

Suggestions

Add a synonym trigger such as 'analytical database' or 'OLAP database' so users who do not name ClickHouse explicitly still match.

Briefly distinguish scope from siblings, e.g. note this is for local/self-hosted dev rather than managed/cloud deploy, to reduce overlap with the clickhousectl-cloud-deploy skill.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('install ClickHouse', 'create a local server', 'create tables', 'set up a local ClickHouse development environment'); not a 5 because 'build an application' and 'start developing' are relatively broad and some coverage is overlapping rather than sharply distinct.	4 / 5
Completeness	An explicit 'Use when a user wants to...' clause supplies the trigger, and the enumerated actions plus 'Covers the full flow from zero to a working local ClickHouse setup' concretely state what the skill does, matching the both-what-and-when anchor.	5 / 5
Trigger Term Quality	Natural phrases a user would say ('install ClickHouse', 'create tables', 'set up a local ... environment') are present; not a 5 because synonyms are limited (e.g. no 'analytical database') and ClickHouse is not file-based so extension-style triggers are absent.	4 / 5
Distinctiveness Conflict Risk	The repeated 'local ClickHouse development' framing carves a clear niche, but closely related sibling skills (cloud-deploy, best-practices) referenced in the body create minor overlap risk, keeping it just below a 5.	4 / 5
	Total	17 / 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: e387359

Reviewed: 3 days 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.