CtrlK
BlogDocsLog inGet started
Tessl Logo

clickhouse

ClickHouse integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClickHouse data.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/clickhouse/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 highly actionable with concrete CLI commands and a well-structured connection workflow including polling feedback loops, but it is let down by an unnecessary concept-explanation intro, a vague overview bullet tree, and a 'Step 2' reference that has no matching labeled section.

Suggestions

Remove or trim the opening 'ClickHouse is a fast open-source...' paragraph and the nested 'ClickHouse Overview' bullet tree; assume Claude knows what ClickHouse is.

Fix the 'skip to Step 2' reference by explicitly labeling the 'Searching for actions' section as Step 2 (or relabel the cross-references).

Show one or two concrete named action examples in 'Popular actions' instead of only repeating the discovery command.

DimensionReasoningScore

Conciseness

The body is mostly actionable CLI commands, but it opens with a concept paragraph explaining what ClickHouse is (which Claude already knows) and includes an odd nested 'ClickHouse Overview' bullet tree plus 'Use action names and parameters as needed' that add little.

3 / 5

Actionability

It provides concrete, copy-paste-ready commands for install, login, connection, action discovery, running actions, and proxying, with a flags table; the minor gap is that 'Popular actions' only re-states the discovery command rather than naming concrete example actions.

4 / 5

Workflow Clarity

The connect-and-poll flow is well sequenced with explicit state checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but an undefined 'Step 2' reference and lack of result-validation for run actions are minor gaps.

4 / 5

Progressive Disclosure

Content is organized into clearly headed sections with no nested/deep references (no bundle files exist), though all reference-y material such as the clientAction state machine and proxy flags table is inlined in a single ~140-line file rather than split out.

4 / 5

Total

15

/

20

Passed

Description

57%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 has an explicit trigger clause and a distinct named-product niche, but its capability phrasing ('manage data, records, and automate workflows') is generic and lacks concrete actions or common query/SQL trigger terms.

Suggestions

Replace generic verbs with concrete ClickHouse actions, e.g. 'Run SQL queries, insert and manage records, and automate data workflows'.

Add natural trigger terms users would say, such as 'query', 'SQL', 'analytics', 'tables', or 'databases'.

Sharpen the 'Use when' clause to name specific intents like 'when the user wants to query or analyze data in ClickHouse'.

DimensionReasoningScore

Specificity

It names the domain ('ClickHouse integration') but the actions are generic ('Manage data, records, and automate workflows') rather than concrete operations like querying, inserting, or analyzing data.

2 / 5

Completeness

It states both what it does ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with ClickHouse data'), though the when could be more specific about analytics/querying use cases.

4 / 5

Trigger Term Quality

'ClickHouse' and 'data'/'records' are relevant keywords, but common natural terms users would say such as 'query', 'SQL', 'database', 'tables', or 'analytics' are missing.

3 / 5

Distinctiveness Conflict Risk

Naming ClickHouse specifically gives it a clear niche with minimal conflict risk, though 'interact with ClickHouse data' could slightly overlap with generic SQL/database skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.