write-script-postgresql

MUST use when writing PostgreSQL queries.

Quality

63%

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-postgresql/SKILL.md

Quality

Content

77%

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

The content is highly actionable and clearly workflow-sequenced with validation checkpoints, and it respects Claude's intelligence by avoiding basic-concept explanations. Its main weakness is conciseness — redundant reminders and asides inflate the token budget — and a somewhat monolithic structure mixing CLI orchestration with PostgreSQL specifics.

Suggestions

Consolidate the repeated "not a deploy" reminders into a single stated-once note; currently this caveat is restated across the preview, generate-metadata, and after-writing sections.

Tighten the generate-metadata prose by moving the version-bump edge cases and parenthetical asides into a short bulleted list or a separate reference, reducing inline length.

Consider splitting the file so the wmill CLI orchestration workflow and the PostgreSQL dialect reference each live in their own clearly-named section or reference file for easier navigation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no explanation of PostgreSQL basics), but it carries repeated "not a deploy" reminders and long parenthetical asides on dependency resolution that could be tightened.	2 / 3
Actionability	It provides fully executable commands (e.g. `wmill script preview <script_path>`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`) and complete, copy-paste-ready SQL examples with parameter binding and the `-- s3` directive.	3 / 3
Workflow Clarity	Multi-step processes are sequenced with explicit validation checkpoints and a feedback loop: edit -> run generate-metadata -> diff regenerated locks -> report bumped versions, plus `--dry-run` to inspect before narrowing scope.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers and one-level-deep external signals (AGENTS.wmill.md, the preview skill), but with no bundle files the single long file mixes two distinct concerns (wmill CLI orchestration and PostgreSQL dialect specifics) that could be split.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 a clear, explicit trigger and a distinct PostgreSQL niche, but it is thin: it names only one action and omits the specific capabilities the skill actually provides. Expanding it to state what it does and covering common trigger variations would lift it.

Suggestions

State the concrete capabilities, e.g. "Write PostgreSQL scripts in Windmill: bind parameters with $1::type, stream results to S3, and sync script metadata. Use when writing or editing PostgreSQL query scripts."

Add common trigger variations users would naturally say, such as "Postgres", "SQL query scripts", or "Windmill PostgreSQL scripts", so the skill triggers on a wider range of phrasings.

Mirror the skill name (write-script-postgresql / Windmill) in the description so it is clearly distinguishable from a generic SQL-query skill.

Dimension	Reasoning	Score
Specificity	"writing PostgreSQL queries" names a concrete domain and one action, but lists only a single action rather than multiple specific capabilities, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It provides an explicit when-trigger ("MUST use when writing PostgreSQL queries") but the 'what' is vague — it never states the actual capabilities (parameter binding, S3 streaming, metadata sync), so only one half is clearly answered.	2 / 3
Trigger Term Quality	The phrase "writing PostgreSQL queries" is natural but offers only one phrasing, with no common variations such as "Postgres", "SQL", or "database queries", matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	PostgreSQL is a distinct niche, but the minimal single trigger could still overlap with broader generic SQL-query-writing skills, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	8 / 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-postgresql/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.