CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-mssql

MUST use when writing MS SQL Server queries.

Quality

63%

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-mssql/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 exact wmill commands and copy-paste MSSQL examples, and the preview/metadata/deploy workflow carries genuine validation checkpoints. Its weaknesses are repeated deploy-vs-preview guidance, off-scope multi-language material inlined in an MSSQL-specific skill, and no use of bundle reference files for the generic Windmill content.

Suggestions

Consolidate the deploy/preview guidance stated in three places ("Deploy local changes", "Preview vs run", "After writing") into one section to remove redundancy.

Move the language-agnostic material (General Principles, Return Values, Preprocessor Scripts, non-MSSQL placeholder syntax) into a shared reference file and keep only the MSSQL section and CLI essentials in SKILL.md.

Reorder the sections chronologically (write → offer/run preview → generate-metadata → deploy) so the workflow reads as one sequence.

DimensionReasoningScore

Conciseness

The body is dense platform-specific knowledge Claude would not know (wmill CLI semantics, lock/hash mechanics, @P1 conventions), not padded with known concepts, but it repeats the deploy/preview distinction in at least three sections ("Deploy local changes...", "Preview vs run", "After writing"), and in an MSSQL skill it inlines placeholder syntax for PostgreSQL/MySQL/Snowflake/BigQuery/Bash/PowerShell plus generic preprocessor material. That is more than the "minor instances of over-explanation" of anchor 4, matching anchor 3 ("Mostly efficient but includes some unnecessary explanation or could be tightened").

3 / 5

Actionability

Guidance is fully executable: exact commands (`wmill script preview <script_path>`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`, `wmill resource-type list --schema`) and copy-paste-ready SQL covering the common cases — @P1 parameter naming comments, `(s3object)` with OPENJSON WITH, and the `-- s3 prefix=... format=parquet` streaming directive. Anchor 5 ("Fully executable; copy-paste ready code or commands; specific examples cover the common cases") is a clear match.

5 / 5

Workflow Clarity

The write → preview (validate) → generate-metadata → deploy-only-on-request workflow is clearly sequenced with real checkpoints: preview validates before any deploy, `--dry-run` lists stale items with reasons, and the lock diff/version-bump report gives a feedback loop. It falls short of anchor 5 because the flow is scattered across four non-chronological sections ("After writing — offer to test" appears after "Keep metadata in sync" though it precedes it in time) and there is no single coherent ordered procedure. Not anchor 3: validation for the risky operation (deploy overwriting the workspace version) is explicitly present, so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the ~119-line single file exceeds the under-50-lines simple-skill exception. The generic Windmill material (CLI commands, General Principles, Return Values, Preprocessor Scripts — covering TypeScript/Python/Go/Rust/etc.) is inline content that belongs in a shared reference file, while repeated pointers to an external `AGENTS.wmill.md` and "the `preview` skill" are not part of this bundle. This matches anchor 3 ("content that should be separate is inline") rather than anchor 2, since section headers and structure are genuinely good.

3 / 5

Total

15

/

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 a strong explicit trigger ("MUST use when writing MS SQL Server queries") but completely lacks a statement of what the skill does, and it omits the Windmill context, creating mis-trigger risk for plain SQL Server work. Keyword coverage is limited to one phrase with no synonyms like T-SQL or MSSQL.

Suggestions

State the 'what' alongside the 'when', e.g. "Write Windmill SQL scripts for Microsoft SQL Server: @P1 parameter naming, S3Object inputs via OPENJSON, streaming results to S3. MUST use when writing MS SQL Server (T-SQL) queries."

Add natural trigger synonyms — "T-SQL", "MSSQL", "SQL Server" — so users' actual phrasing matches the description.

Scope the trigger to the Windmill context so a plain "write me a SQL Server query" request outside Windmill does not pull in this skill.

DimensionReasoningScore

Specificity

The description names the domain ("writing MS SQL Server queries") but lists zero concrete actions or capabilities — it says nothing about what the skill actually does (arg parsing via @P1, S3Object parameters, streaming results to S3). It matches anchor 2 ("Names the domain but actions are minimal or generic"): it is not entirely vague like anchor 1, but unlike anchor 3 it names no concrete actions at all.

2 / 5

Completeness

The description gives only a 'when' clause ("MUST use when writing MS SQL Server queries") with no 'what' at all — the skill's purpose (writing Windmill SQL scripts in the MSSQL dialect) is never stated. This is exactly anchor 2's case ("only 'when' is present without 'what'"); it cannot reach anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"MS SQL Server queries" is a natural phrase a user would say, but it is the only keyword phrase present; common variants users actually type — "T-SQL", "MSSQL", "SQL Server", "stored procedure", "Transact-SQL" — are missing. This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than anchor 4's broader multi-keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"MS SQL Server queries" is fairly specific, but the description omits the Windmill context entirely, so it would trigger for any generic SQL Server query request where a Windmill-specific skill is wrong. Anchor 3 ("Somewhat specific but could still overlap with similar skills") fits: it also risks collision with sibling dialect skills (PostgreSQL/MySQL versions) that would share near-identical phrasing.

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