CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-duckdb

MUST use when writing DuckDB queries.

Quality

63%

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 ./system_prompts/auto-generated/skills/write-script-duckdb/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 delivers strong, concrete Windmill/DuckDB guidance with real validation checkpoints around preview, metadata regeneration, and deploy gating — clearly actionable. Its weaknesses are repetition (deploy caution stated three times, over-dense bullets) and the inlining of the general Windmill script-writing guide, which should be split into a reference file so SKILL.md stays a focused overview for the DuckDB dialect. No bundle files exist, so all content is carried in the main file.

Suggestions

State the deploy-only-on-explicit-ask rule once (in the CLI command list) and reference it from the other sections instead of restating it three times.

Move the 'Windmill Script Writing Guide' (General Principles, Return Values, Preprocessor Scripts) into a references/ file (e.g. references/windmill-script-writing.md) and keep a short overview with a clearly signaled link in SKILL.md, keeping the main file focused on the DuckDB dialect.

Show one complete concrete preview invocation (e.g. wmill script preview f/my/script -d '{"name": "alice", "age": 30}') so the argument-passing shape is copy-paste ready rather than implied.

DimensionReasoningScore

Conciseness

The deploy-only-on-explicit-ask caution is repeated three times (the CLI list, 'Preview vs run', and the 'After writing' section), and several bullets are dense multi-clause paragraphs (the custom-resource-type bullet, the metadata-sync paragraph) that could be tightened. Most content is non-obvious Windmill-specific knowledge rather than filler, so this lands at 'Mostly efficient but includes some unnecessary explanation or could be tightened', not the padded verbosity of score 2.

3 / 5

Actionability

Concrete, runnable commands appear throughout ('wmill script preview <script_path>', 'wmill generate-metadata --dry-run', 'wmill generate-metadata rehash', 'wmill resource-type list --schema') and the SQL blocks are executable ('ATTACH \'ducklake\' AS dl;', 'COPY (SELECT * FROM users) TO \'s3:///exports/users.parquet\' (FORMAT PARQUET)'). Minor gaps keep it below fully copy-paste-ready: the '-d \'<args>\'' preview invocation is described but never shown as a concrete example, and placeholder syntaxes for other dialects are listed where DuckDB is the skill's focus.

4 / 5

Workflow Clarity

The write → preview → generate-metadata → deploy-only-when-asked flow has real decision rules (preview vs run chosen by intent, sync push only on explicit ask) and genuine validation checkpoints: preview validates before any deploy, 'diff the regenerated .lock / .script.lock files and tell the user which dependency versions changed', and '--dry-run ... lists each stale item with a reason'. It falls short of score 5 because the sequence is scattered across four separate sections rather than presented as one coherent ordered workflow with error-recovery loops.

4 / 5

Progressive Disclosure

The skill is ~150 lines with no bundle files, and the entire general 'Windmill Script Writing Guide' (General Principles, Return Values, Preprocessor Scripts) is inlined — content that belongs in a separate reference file for a skill named write-script-duckdb. Navigation points outward to project files ('see the Deploying section in AGENTS.wmill.md', the 'preview' skill) rather than to organized bundle references, matching 'content that should be separate is inline' rather than the well-split structure of score 4.

3 / 5

Total

14

/

20

Passed

Description

43%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 distinctive and has a valid trigger clause, but it omits any statement of what the skill actually does and gives Claude no capability list to act on. It reads as a bare trigger rather than a description. The high distinctiveness of the DuckDB niche keeps it from scoring poorly overall, but completeness and specificity are the weak points.

Suggestions

Add a 'what' clause listing concrete capabilities, e.g. 'Write Windmill scripts in the DuckDB SQL dialect: define $name arguments, attach ducklake and external Postgres databases, and read/write S3 files (CSV, Parquet, JSON). MUST use when writing DuckDB queries.'

Include natural trigger synonyms such as 'SQL', 'database queries', or '.duckdb' so the skill fires on the phrasings users actually say.

Keep the third-person, action-led style ('Writes...', 'Attaches...') while adding these capabilities so the description answers both 'what' and 'when' explicitly.

DimensionReasoningScore

Specificity

The description 'MUST use when writing DuckDB queries' names a concrete domain (DuckDB queries) but lists zero concrete actions or capabilities. It matches the anchor 'Names the domain but actions are minimal or generic' — not score 1 because the domain is specific rather than pure abstraction, and not score 3 because no actions whatsoever are described.

2 / 5

Completeness

Only a 'when' is present ('when writing DuckDB queries') with no 'what' — the description never says what the skill does (write Windmill scripts in the DuckDB dialect, run previews, sync metadata, query S3/ducklake). This is exactly the anchor 'only when is present without what'; score 3 requires a clear 'what', which is entirely missing.

2 / 5

Trigger Term Quality

'DuckDB' and 'queries' are natural terms a user would say, but common variations and synonyms ('SQL', 'database', '.duckdb', 'SELECT') are absent. This matches 'Some relevant keywords but missing common variations or synonyms' rather than the good coverage of score 4.

3 / 5

Distinctiveness Conflict Risk

DuckDB is a clear, niche technology with distinct triggers, so the description is unlikely to fire for unrelated skills — matching the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

12

/

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

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/write-script-duckdb/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.