CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-powershell

MUST use when writing PowerShell scripts.

Quality

61%

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-powershell/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 delivers genuinely valuable, concrete Windmill platform workflow guidance with good decision rules and validation checkpoints, but it mixes general Windmill content into a PowerShell-specific skill, repeats key caveats, and teaches basic PowerShell syntax. Most importantly, it never shows the PowerShell-specific resource-typed parameter pattern its own General Principles section promises, leaving the skill's core credential-handling story incomplete for its target language.

Suggestions

Add a PowerShell example showing a resource-typed parameter (and wmill client usage if supported), since General Principles explicitly promise the language section shows how credentials are declared but the PowerShell section only demonstrates generic param syntax.

Move the general Windmill content (preprocessor scripts, all-language principles, other languages' placeholder syntax) into a shared reference file and keep only PowerShell-specific guidance inline, fixing the heading hierarchy so H1 sections precede their H2 children.

State the deploy-vs-test and not-a-deploy caveat once in a single location instead of repeating it across three sections, and trim the basic PowerShell type/return explanations Claude already knows.

DimensionReasoningScore

Conciseness

The wmill CLI semantics (preview vs run vs sync push, generate-metadata/rehash) is non-obvious platform knowledge that earns its tokens, but the 'not a deploy' caveat is repeated three times, the PowerShell section re-explains basic PowerShell Claude already knows (param syntax, typed parameters, outputting objects), and the body inlines other languages' placeholder syntax ($1 for PostgreSQL, ? for MySQL, @P1 for MSSQL, positional $1/$2 for Bash). Mostly efficient with unnecessary explanation that could be trimmed fits anchor 3 rather than 4 (the over-explanation is more than minor) or 2 (the bulk is novel, not padded).

3 / 5

Actionability

Concrete copy-paste commands appear throughout ("wmill script preview <script_path>", "wmill generate-metadata --dry-run", "wmill resource-type list --schema") and the PowerShell snippets are executable. The key gap: General Principles promise "the language section below shows how that language declares parameters" for resource-typed credentials, but the PowerShell section never shows a resource-typed parameter or wmill client usage — only generic param($Name, [int]$Age) examples. Mostly executable guidance with minor gaps fits anchor 4, falling short of 5's fully covered common cases.

4 / 5

Workflow Clarity

Clear intent-based decision rules (preview when local edits exist; run only for the deployed version; sync push only on explicit deploy request) plus feedback checkpoints: preview validates before deploy, --dry-run lists each stale item with a reason, and the user should diff regenerated .lock files and report version bumps. It falls short of anchor 5 because the write → preview → generate-metadata → diff → deploy sequence is distributed across four sections rather than presented as one ordered flow, and "Place scripts in a folder" is vague about which folder.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content is inlined in a single ~130-line file with a broken heading hierarchy (H2 "CLI Commands" sections precede a later H1 "Windmill Script Writing Guide"). Roughly 40% of the body is general Windmill content — preprocessor scripts, all-language principles, other languages' placeholder syntax — that belongs in a shared reference rather than the PowerShell-specific skill. Some structure exists with usable section headers, fitting anchor 3 rather than 2.

3 / 5

Total

14

/

20

Passed

Description

40%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 minimal trigger-only statement: it says when to use the skill but nothing about what the skill does, and omits the Windmill platform context entirely. Its one strength is a distinct, low-conflict trigger phrase. It needs a concrete capability statement to be complete.

Suggestions

State what the skill does in third person, e.g. "Writes Windmill scripts in PowerShell: param-based arguments, resource-typed credentials, preview and metadata regeneration via the wmill CLI. MUST use when writing PowerShell scripts for Windmill."

Add natural trigger variations such as ".ps1", "pwsh", and "PowerShell" alongside "PowerShell scripts" so users phrasing the request differently still match.

Mention the Windmill context explicitly to prevent the description from matching generic (non-Windmill) PowerShell scripting requests.

DimensionReasoningScore

Specificity

"MUST use when writing PowerShell scripts." names the domain but lists zero concrete actions — it never mentions Windmill, param declaration, resource-typed credentials, or the preview/metadata workflow the skill actually covers. This matches the anchor 'names the domain but actions are minimal or generic'; it is not a 1 because the domain is explicitly named, and not a 3 because no concrete action is stated at all.

2 / 5

Completeness

An explicit 'when' is present ("when writing PowerShell scripts") but the 'what' is entirely absent — the description never states what the skill does (write Windmill platform scripts in PowerShell). This matches anchor 2 ('only when is present without what'); anchor 3 requires a clear 'what', which is missing.

2 / 5

Trigger Term Quality

"writing PowerShell scripts" includes the natural keyword "PowerShell", but misses common variations users would say such as ".ps1", "pwsh", or "PowerShell module". This fits 'some relevant keywords but missing common variations or synonyms'; a 4 would require broader keyword coverage than a single substantive term.

3 / 5

Distinctiveness Conflict Risk

"PowerShell scripts" is a distinct niche unlikely to trigger unrelated skills, but the bare single trigger has minor overlap risk with generic shell-scripting skills and sibling Windmill language skills (the description does not even name Windmill). Mostly distinct with minor overlap risk fits anchor 4 rather than the clear-niche anchor 5.

4 / 5

Total

11

/

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