CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clickhouse-migrations

ClickHouse migration patterns and rules. Use when creating or modifying ClickHouse migrations.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

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 high-quality reference-style skill body: almost every line carries non-obvious operational rules, with concrete code, exact file paths, and real validation gates (live-cluster checks, check.sh exit 0, test_migrations.py coverage). The only notable weaknesses are placeholder-laden core template snippets and topic- rather than sequence-oriented organization that leaves the end-to-end workflow to be inferred.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific facts Claude cannot know (node-role ownership rules, Kafka settings defaults, the run_mode gating table, the schema.py tuple table) and assumes competence — it never explains what ClickHouse or a migration is. A few passages could still be tightened, e.g. the very long CODEC bullet and the node-roles section repeating 'check where the object is read and written', which places it at anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than anchor 5.

4 / 5

Actionability

Most guidance is executable: copy-paste-ready Kafka SETTINGS SQL, the run_mode gating snippet, exact engine signatures, the schema.py tuple table, and the HCL shell commands (`bash $HCL/gen-golden.sh && bash $HCL/gen-sql.sh`, `check.sh`). The anchor-4 fit comes from the core migration template containing placeholders (`SQL_FUNCTION()`, `node_roles=[...]`) and `hclexp locate` being invoked without any setup or usage pointer — minor gaps that keep it below fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Sequences with explicit checkpoints are present despite the destructive/batch nature of migrations: a numbered pre-flight live-cluster check across dev/prod-us/prod-eu (including verifying new table names are unused), `check.sh # must exit 0` as a hard validation gate, and the two-step DROP COLUMN process with team coordination and a named CI failure mode (`DRIFT:` block) for feedback. It sits at anchor 4 rather than 5 because the sections are topic-organized rather than one end-to-end ordered workflow — the reader must assemble the order (check clusters → choose role → write migration → update schema.py → update HCL → check.sh → PR) themselves.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body appropriately defers the bulk of detail to one-level-deep, clearly signaled external files: AGENTS.md is pointed to up front ('comprehensive patterns, cluster setup, examples, and ingestion layer details') and again at the Kafka section ('has the sizing rules and the rest'), plus hcl/README.md, connection.py, and a runbook link — each with a stated reason to open it. The inline content is a genuine quick reference with clean section navigation and no nested references, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

73%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 concise, well-targeted description with an explicit and appropriately narrow 'Use when' clause and essentially no conflict risk. Its main weakness is a generic 'what' — 'patterns and rules' — that never states the skill's concrete capabilities.

Suggestions

Name 2-3 concrete capabilities in the 'what' clause, e.g. 'Write ClickHouse migrations: pick node roles, structure run_sql_with_exceptions operations, and keep HCL golden files in sync. Use when creating or modifying ClickHouse migrations.'

Add one or two natural trigger variations users might say, such as 'schema change' or 'ClickHouse table', to the 'Use when' clause.

DimensionReasoningScore

Specificity

The description names the domain precisely ("ClickHouse migration patterns and rules") and the 'Use when' clause adds action context ("creating or modifying ClickHouse migrations"), but the stated capability itself — 'patterns and rules' — is generic and lists no concrete capabilities such as choosing node roles, writing migration operations, or syncing HCL golden files. It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is above anchor 2 because the create/modify scope is concrete, and below anchor 4 because no specific actions are enumerated.

3 / 5

Completeness

Both parts are present: 'what' = "ClickHouse migration patterns and rules", and an explicit 'when' = "Use when creating or modifying ClickHouse migrations". The 'when' is concrete and explicit, but the 'what' is general ('patterns and rules') without saying what the skill actually does, matching anchor 4 ('has both what and when; when could be more explicit or specific') — here it is the 'what' that keeps it below anchor 5 rather than the 'when'.

4 / 5

Trigger Term Quality

Natural terms a user would say are present: 'ClickHouse', 'migration', 'creating', 'modifying' — matching the trigger phrasing a developer would actually use. It falls at anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5 because common variations like 'schema change', 'table', or 'ALTER' are absent, and above anchor 3 because both the create and modify variants are covered rather than a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

"ClickHouse migration" is a clear niche with distinct triggers and minimal overlap with any other plausible skill — a user asking about ClickHouse migrations would land here unambiguously. It matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PostHog/posthog

Path

.agents/skills/clickhouse-migrations/SKILL.md

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.