write-script-mysql

MUST use when writing MySQL queries.

Quality

65%

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

Quality

Content

82%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 content is highly actionable and well-structured with strong validation guidance for a destructive-capable workflow, penalized mainly for repetition of the preview/deploy guidance and topical rather than sequential organization.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational, explaining Windmill-specific behavior Claude would not already know, but the preview-vs-deploy distinction is restated across several sections and could be consolidated to trim tokens.	4 / 5
Actionability	It provides copy-paste-ready SQL examples (parameter binding, JSON_TABLE S3Object ingest, s3 streaming directive) and concrete CLI commands covering the common cases.	5 / 5
Workflow Clarity	The write → sync-metadata → preview → deploy-only-when-asked sequence is clear with explicit validation checkpoints (generate-metadata --dry-run, diffing lock files, preview before deploy), though it is organized topically rather than as an explicit numbered sequence.	4 / 5
Progressive Disclosure	The single ~90-line file is well-sectioned with clearly signaled one-level-deep references (AGENTS.wmill.md, the preview skill); no bundle files exist, but the general Windmill workflow is inlined where a separate shared reference might help.	4 / 5
	Total	17 / 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 is a terse trigger clause that fires correctly for MySQL query work but never states what the skill actually does. Expanding it to name concrete capabilities alongside the trigger would lift completeness and specificity.

Suggestions

Add a "what" clause listing concrete capabilities, e.g. "Write Windmill MySQL scripts: bind ? parameters, ingest S3Object inputs via JSON_TABLE, and stream results to S3."

Broaden trigger terms to include natural synonyms like "SQL queries" or "database queries" so users who don't say "MySQL" still match.

Keep the explicit "Use when..." trigger but pair it with the capability list so both what and when are answered explicitly.

Dimension	Reasoning	Score
Specificity	The description "MUST use when writing MySQL queries" names the domain (MySQL queries) but offers only one minimal, generic action ("writing") that essentially restates the skill name rather than enumerating concrete capabilities.	2 / 5
Completeness	It has an explicit "when" trigger ("MUST use when writing MySQL queries") but only weakly implies the "what" — no statement of capabilities like generating, validating, or parameter-binding queries is given.	3 / 5
Trigger Term Quality	It includes the natural keyword "MySQL queries", but misses common variations and synonyms a user might say such as "SQL", "database queries", or "queries".	3 / 5
Distinctiveness Conflict Risk	"MySQL queries" is a clear niche with minimal conflict risk, though it could overlap slightly with sibling SQL-dialect skills (e.g. PostgreSQL, Snowflake) referenced in the body.	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-mysql/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.