CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chdb-arrow

Choose chDB Python Arrow input, result, insert, or standard Arrow database-driver paths when a task uses PyArrow tables or readers. Not for ordinary SQL or DataStore work.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean, information-dense routing skill: nearly every line carries chDB-specific facts Claude would not know, and each Arrow route gets a concrete API call. The main weaknesses are the missing validation step for the batch bulk-insert operation (capping workflow clarity) and code templates with placeholders plus an external docs reference that does not resolve inside the skill bundle.

Suggestions

Add a verification step after bulk inserts (e.g. compare "chdb.query('SELECT count() FROM dst')" against the source table's row count) so the batch operation has an explicit validation checkpoint.

Replace one "SELECT ..." placeholder with a complete runnable statement (e.g. a full query over Python(tbl) with real column names) so the primary pattern is copy-paste ready.

Make the documentation pointer resolvable: either place querying-apache-arrow guidance in a references/ file in the skill bundle, or state explicitly that docs/guides/querying-apache-arrow.mdx lives in the chDB repository.

DimensionReasoningScore

Conciseness

The body is dense with chDB-specific, non-generic facts ("path=data_path", "keep the source alive through the query", "BindStream ... binds parameters, not a temporary table in FROM") that Claude could not know. Minor over-explanation remains: "a `RecordBatchReader` is a one-shot source of batches" restates basic PyArrow knowledge, and the ADBC-is-separate point is made in both the intro and the final bullet, so anchor 4 fits better than the every-token-earns-its-place bar of 5.

4 / 5

Actionability

Concrete API calls are given ("chdb.query(\"SELECT ... FROM Python(tbl)\")", "chdb.query_arrow(sql)", "with chdb.query_arrow_batches(sql) as batches:"), including the load-bearing kwarg "path=data_path". The "SELECT ..." and "dst" placeholders keep the snippets from being fully copy-paste ready, matching anchor 4 (concrete code with minor gaps) rather than 5.

4 / 5

Workflow Clarity

The scenario bullets (query, bulk insert, typed results, ADBC route) form a clear routing decision, but "Bulk insert into an existing table" is a batch database operation with no validation or verification step (e.g. checking row counts or errors after insert). Per the rubric guideline, batch/database operations without validation cap workflow clarity at 3, taking precedence over the simple-skill exception.

3 / 5

Progressive Disclosure

The skill is under 50 lines with content appropriately inline and one clearly signaled reference ("Start with docs/guides/querying-apache-arrow.mdx"). However, no bundle files exist (no references/ directory), so the referenced path does not resolve within the skill, and the routes are un-headered bullets rather than sections — good structure with minor organization gaps, matching anchor 4 rather than the clean 5.

4 / 5

Total

15

/

20

Passed

Description

87%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 strong description: it names a clear niche, gives an explicit 'when' trigger tied to PyArrow tables/readers, and adds a negative boundary to avoid mis-triggering. Keyword coverage is good though it omits ADBC and RecordBatch synonyms, and the capability phrasing ('choose ... paths') is slightly more abstract than concrete API verbs.

DimensionReasoningScore

Specificity

"input, result, insert, or standard Arrow database-driver paths" enumerates four concrete route types tied to "PyArrow tables or readers", matching the anchor for several specific actions with minor gaps. Not 5 because "Choose ... paths" is one abstract verb over enumerated objects rather than multiple concrete API actions (e.g. query_arrow), and not 3 because it lists well more than 1-2 concrete items.

4 / 5

Completeness

The what ("Choose chDB Python Arrow input, result, insert, or standard Arrow database-driver paths") and the when ("when a task uses PyArrow tables or readers") are both explicit, with concrete trigger phrases plus a negative boundary ("Not for ordinary SQL or DataStore work"). This matches anchor 5; a 4 would require the when to be only implicit or less specific.

5 / 5

Trigger Term Quality

Natural trigger terms like "chDB", "PyArrow tables or readers", and "Arrow" are present and would be said by users needing this skill. A few natural terms are missing (ADBC, RecordBatch, .arrow files), which matches the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive synonym/extension coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is tightly scoped to chDB + PyArrow and the explicit exclusion "Not for ordinary SQL or DataStore work" prevents overlap with generic SQL skills. Clear niche with distinct triggers and minimal conflict risk matches anchor 5.

5 / 5

Total

18

/

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

chdb-io/chdb

Path

.agents/skills/chdb-arrow/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.