BD clickhouse-js-node-coding
Write idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js client — configuring the client, pinging, inserting rows in JSON or raw formats, selecting and parsing results, binding query parameters, managing sessions and temporary tables, working with data types or customizing JSON parsing. Do NOT use for browser/Web client code.
Write idiomatic application code with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user is building against the Node.js…
As a process D 42/100 · Unfinished process — References files that are not bundled: examples/node/performance/, examples/node/security/, examples/node/schema-and-deployments/
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/node/performance/ - warning
missing-refreference to a missing file: examples/node/security/ - warning
missing-refreference to a missing file: examples/node/schema-and-deployments/ - warning
missing-refreference to a missing file: examples/web/ - warning
missing-refreference to a missing file: examples/node/coding/ - note
edit-residuethe text marks something as outdated (lines 26): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 42/100
- 0Tools and files. 5 referenced file(s) missing: examples/node/performance/, examples/node/security/, examples/node/schema-and-deployments/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 12 mutating operations with no state check
- 85Steps. 33 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2659 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 427: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 33 items
- +4Reference files are cited in the instructions (12 of 12)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.