write-script-csharp

MUST use when writing C# scripts.

Quality

55%

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-csharp/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 delivers highly actionable, executable guidance with real validation checkpoints for a mutating workflow, though it is somewhat repetitive and discursive rather than tightly sequenced. Structure and reference signaling are solid for a single-file skill with no bundle.

Suggestions

Consolidate the repeated 'only deploy on explicit ask' rule into a single stated caveat and reference it, rather than restating it in the preview, sync push, and after-writing sections.

Surface the write → generate-metadata → preview → (deploy) sequence as a short numbered checklist near the top so the workflow is immediately legible before the prose detail.

Consider moving the extended metadata-sync detail (hash drift, import propagation, --strict-folder-boundaries) into a references file and keeping SKILL.md to the core commands.

Dimension	Reasoning	Score
Conciseness	Most content is wmill-specific operational knowledge Claude would not know, but the 'only deploy on explicit ask' caveat is repeated in at least four places (lines 15, 19, 26, 45) and some sentences could be tightened.	3 / 5
Actionability	Commands are concrete and copy-paste ready (`wmill script preview <script_path>`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`), and the C# examples (public static Main, NuGet #r directive) are fully executable and cover the common cases.	5 / 5
Workflow Clarity	A clear sequence exists (write → sync metadata → preview to validate → deploy only when asked) with validation checkpoints (preview, --dry-run, diffing .lock files), so the destructive/batch cap does not apply; it is presented discursively rather than as a crisp numbered checklist.	4 / 5
Progressive Disclosure	The body is well-sectioned with clear headers and signals external references (AGENTS.wmill.md 'Deploying' section, the preview skill); no bundle files exist, and the single-file structure with organized sections is appropriate for this length, with only minor organization gaps.	4 / 5
	Total	16 / 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 is a terse trigger-only sentence that states when to use the skill but never says what it does. It is distinguishable enough by language but lacks any capability detail and offers only a single trigger phrase.

Suggestions

Add a 'what' clause listing concrete capabilities, e.g. 'Writes Windmill C# scripts with a public static Main method, manages NuGet #r imports, and keeps .script.yaml/.lock metadata in sync via wmill CLI.'

Expand trigger coverage with synonyms and file extensions: 'Use when writing or editing C# scripts (.cs) for Windmill, adding NuGet packages, or regenerating script metadata.'

Mention the wmill/Windmill context so the skill does not collide with general C# coding skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("writing C# scripts") but provides no concrete actions or capability verbs at all — it never says what the skill does, only when to trigger it.	2 / 5
Completeness	Only the "when" is present ("MUST use when writing C# scripts"); the "what" is entirely absent, matching the anchor where only the trigger is stated without describing the skill's function.	2 / 5
Trigger Term Quality	"writing C# scripts" is a natural phrase a user would say, but coverage stops there — no synonyms or file extensions like ".cs", "C# code", or "dotnet scripts" are included.	3 / 5
Distinctiveness Conflict Risk	"writing C# scripts" is somewhat specific, but with no mention of the wmill/Windmill automation context it could still overlap with generic C# development skills.	3 / 5
	Total	10 / 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-csharp/SKILL.md
Commit: 74af4ed

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