write-script-duckdb

MUST use when writing DuckDB queries.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, highly actionable, and pairs concrete commands with executable SQL plus a clear metadata-sync workflow that includes verification checkpoints. The only weakness is progressive disclosure: everything lives inline with no bundle files to offload the wmill-CLI detail.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and assumes Claude's competence — it never explains basic concepts, and nearly every line is domain-specific wmill/DuckDB knowledge or executable syntax that earns its tokens. It does not reach below 3 because there is no padding or generic explanation to trim.	3 / 3
Actionability	It provides concrete, copy-paste-ready commands (`wmill script preview`, `wmill generate-metadata`, `wmill generate-metadata rehash`) and complete executable SQL examples with exact argument and reader syntax, matching the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The metadata-sync flow is clearly sequenced with explicit verification checkpoints — run generate-metadata, diff the regenerated `.lock`/`.script.yaml`, report version bumps, and use `--dry-run` to inspect stale items before narrowing — matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the body is monolithic (no bundle files exist in references/scripts/assets) and exceeds 50 lines; the only cross-references are external project files (AGENTS.wmill.md, the preview skill) rather than a one-level-deep bundle, so it stops at 'some structure but could be better organized'.	2 / 3
	Total	11 / 12 Passed

Description

57%

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 and a distinct DuckDB niche, but it is thin: it names only one action and merges 'what' with 'when' rather than stating concrete capabilities. It reads more as a trigger clause than a capability description.

Suggestions

Add 2-3 concrete capabilities, e.g. "Write DuckDB queries in Windmill scripts, attach Ducklake and external databases, and read/write S3 files."

Keep the explicit "Use when writing DuckDB queries" trigger but separate it from the capability list so the 'what' is distinct from the 'when'.

Include a few natural term variations ("DuckDB", "DuckDB SQL", "queries") so the trigger matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ("writing DuckDB queries"), matching the anchor that names a domain and some actions, but it lists only a single action rather than multiple specific capabilities, so it does not reach level 3.	2 / 3
Completeness	An explicit trigger is present ("MUST use when writing DuckDB queries"), but the 'what' is only implied and circular with the trigger — it never states distinct capabilities the skill performs, so it falls short of clearly answering both what and when.	2 / 3
Trigger Term Quality	"DuckDB queries" is a natural term a user would say, but the description offers only that single keyword with no common variations (e.g. "duckdb", "SQL", "queries"), matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	DuckDB is a clear, narrow niche with a distinct trigger unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 33d2845

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.