write-script-postgresql

MUST use when writing PostgreSQL queries.

Quality

61%

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

75%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 is highly actionable with executable commands and complete SQL examples, and it sequences a non-trivial workflow with real validation checkpoints for the destructive/batch steps. It is somewhat verbose due to repeated deploy guidance and could split the PostgreSQL reference material, but overall well-structured.

Dimension	Reasoning	Score
Conciseness	The body is largely dense and avoids explaining basics, but deploy guidance ('git push or wmill sync push ... see the Deploying section') is restated across several sections and passages like the import-propagation explanation run long, so it could be tightened.	3 / 5
Actionability	Concrete executable commands (`wmill script preview`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`, `wmill resource-type list --schema`) and complete, copy-paste-ready SQL examples cover parameter binding, S3Object ingestion, and S3 streaming.	5 / 5
Workflow Clarity	The write → choose-preview-by-intent → sync-metadata → offer-test → deploy-only-when-asked flow has explicit checkpoints (diff regenerated locks, --dry-run stale listing, explicit-ask gate for the destructive deploy), though it is not presented as a single linear checklist.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but the single SKILL.md is well-organized with clear section headers and signals external references explicitly ('see the Deploying section in AGENTS.wmill.md'); the inlined PostgreSQL detail is the main organization gap.	4 / 5
	Total	16 / 20 Passed

Description

48%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 has an explicit trigger but is circular — the stated capability ('writing PostgreSQL queries') restates the trigger and omits the skill's real scope (Windmill scripts, S3 handling, streaming). It is moderately distinct and actionable enough to trigger correctly, but undersells what the skill covers.

Suggestions

Rewrite to state concrete capabilities, e.g. 'Write Windmill PostgreSQL scripts: bind parameters with $1::TYPE, receive S3Objects as jsonb, and stream large results to S3. Use when creating or editing PostgreSQL scripts in a Windmill workspace.'

Add natural synonyms users say — 'PostgreSQL', 'SQL', 'Postgres', 'queries' — to improve trigger term coverage.

Decouple the 'what' from the 'when' so the description answers both distinctly instead of restating the trigger.

Dimension	Reasoning	Score
Specificity	The phrase 'writing PostgreSQL queries' names the domain but gives only one generic action with no concrete capabilities (e.g. parameter binding, S3 streaming) listed, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	An explicit 'use when' clause is present, but the 'what' is essentially identical to the trigger (circular) and never states the skill's actual purpose (Windmill PostgreSQL scripts), so it only weakly answers what the skill does.	3 / 5
Trigger Term Quality	'PostgreSQL queries' is a natural term users would say, but the description lacks common synonyms/variations (SQL, Postgres, .sql, pg), fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'PostgreSQL queries' carves a clear niche with only minor overlap risk against generic SQL or database skills; the lack of Windmill context keeps it just short of fully distinct.	4 / 5
	Total	12 / 20 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: 74af4ed

Reviewed: about 18 hours 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.