CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-mysql

MUST use when writing MySQL queries.

Quality

60%

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-mysql/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 is a strong operational guide: concrete commands, copy-paste SQL examples, explicit decision rules, and real validation checkpoints (dry-run, lock diffing, preview-before-deploy). Its weaknesses are repetition and dense prose that could be tightened, a missing example for the most common MySQL case (declaring the database connection as a resource parameter), and substantial generic platform content inlined where a shared reference would keep the MySQL skill lean.

Suggestions

State the 'it is not a deploy' rule once (e.g. in the command list) and remove the repetitions in the metadata-sync and after-writing sections; split long parenthetical-heavy paragraphs into short imperative bullets.

Add a concrete MySQL example showing how a script declares its database connection (resource-typed parameter syntax for SQL) and a worked 'wmill script preview <path> -d ...' invocation with real placeholder args.

Move the language-agnostic Windmill content (General Principles, Return Values, Preprocessor Scripts) into a shared reference file and keep only the MySQL-specific guidance plus a clearly signaled pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational guidance rather than known-concept padding, but it is noticeably repetitive and could be tightened: 'not a deploy' is restated three times (lines 14, 31, and 45), and several long run-on paragraphs (e.g. the metadata-sync and resource-type guidance) bury key rules in qualifiers. It sits above anchor 2 because most content earns its tokens, and below anchor 4 because the repetition and parenthetical-heavy prose are real trimming opportunities.

3 / 5

Actionability

Guidance is mostly executable: concrete wmill commands with flags ('wmill script preview <script_path>', 'generate-metadata --dry-run', 'rehash', 'resource-type list --schema') and copy-paste-ready SQL examples for parameter naming, JSON_TABLE/S3Object consumption, and the '-- s3' streaming directive. It falls short of anchor 5 because the most common case — how a MySQL script declares its database connection/resource-typed parameter — is never shown in the SQL section, and the preview invocation 'wmill script preview <path> -d '<args>'' lacks a concrete worked example.

4 / 5

Workflow Clarity

The workflow (write → preview locally → generate-metadata after edits → deploy only on explicit request) is clearly sequenced with decision rules for preview vs run vs sync push, and genuine checkpoints are present: dry-run to inspect stale items before regenerating, diffing the regenerated locks and reporting version changes, preview validating before any deploy, and confirming before side-effecting execution. Because validation is present, the database-operations cap at 3 does not apply; it misses anchor 5 mainly because the end-to-end flow must be assembled from separate sections rather than one explicit sequence.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the skill is over 50 lines and inlines roughly 40 lines of generic Windmill platform content (General Principles, Return Values, Preprocessor Scripts, multi-language entrypoint details) that belongs in a shared reference file for a MySQL-specific skill. The only external pointers ('AGENTS.wmill.md', the 'preview' skill) are to files outside the bundle. This matches anchor 3 — 'content that should be separate is inline' — rather than anchor 4's 'most content is appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

36%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, well-formed trigger clause and the key domain term, but it completely omits the 'what' — the skill's concrete capabilities are never stated, and trigger coverage is a single keyword. It functions as a bare trigger line rather than a capability description, and would fire on any MySQL request regardless of whether the Windmill-specific skill applies.

Suggestions

Add a 'what' clause naming the concrete capability, e.g. 'Write MySQL scripts for Windmill: parameterized queries with ? placeholders, S3Object inputs, and result streaming to S3. MUST use when writing MySQL queries or SQL scripts for Windmill.'

Broaden trigger terms with natural synonyms users would say: 'SQL query', 'database query', 'SELECT', and '.sql' alongside 'MySQL queries'.

Include the Windmill context in the trigger so the skill does not fire on generic MySQL help outside its scope (e.g. 'when writing MySQL scripts for Windmill').

DimensionReasoningScore

Specificity

The description names a concrete domain ("writing MySQL queries") but lists no actions at all — what the skill actually does (write MySQL scripts for Windmill) is entirely unstated. It is above anchor 1 because the domain is concrete rather than pure abstraction, and below anchor 3 because no concrete capability is named.

2 / 5

Completeness

"MUST use when writing MySQL queries" provides an explicit 'when' but no 'what' — the description never states what the skill does. Anchor 2 ('only when is present without what', e.g. 'Use when working with documents') is the exact match; anchor 3 requires a clear 'what', which is absent.

2 / 5

Trigger Term Quality

"MySQL" and "queries" are natural terms a user would say, but coverage rests on essentially one keyword, missing common variations like "SQL", "database", "SELECT", or ".sql". This matches 'some relevant keywords but missing common variations or synonyms' rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

MySQL is a specific domain, but the description carries no Windmill context, so it would trigger on any MySQL query request — including plain query help well outside the skill's actual scope — creating overlap risk with generic SQL skills. Somewhat specific but could still overlap with similar skills.

3 / 5

Total

10

/

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