CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-csharp

MUST use when writing C# scripts.

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-csharp/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 strong, executable operational guidance — exact CLI commands, a well-reasoned preview/deploy decision workflow with real validation checkpoints, and complete C# code examples. Its weaknesses are structural: generic multi-language Windmill content is inlined in a language-specific skill, and the C# section itself misses how resource-typed parameters are declared in C#.

Suggestions

Move the language-agnostic "Windmill Script Writing Guide" (General Principles, Return Values, Preprocessor Scripts) into a shared reference file (e.g. references/windmill-script-guide.md) and keep only the C# section inline.

Add a C# example showing how a resource-typed parameter is declared in a `Main` signature, since only the TypeScript (`RT.C<Name>`) and Python (`c_<name>` TypedDict) forms are shown.

Trim the multi-language argument-shape list (SQL `$1`/`@P1`/`@name`, Bash positional, PowerShell `param(...)`) to a pointer to the shared guide — it is irrelevant to C# scripting.

DimensionReasoningScore

Conciseness

The CLI-workflow material (preview vs run, generate-metadata, hash syncing) is dense and high-value with no padding about concepts Claude already knows. However, roughly a third of the body is other-language content inlined into a C# skill — TS/Python preprocessor typing, SQL `@P1`/BigQuery placeholder syntax, Bash/PowerShell argument shapes — which is more than a minor trim, keeping it below anchor 4.

3 / 5

Actionability

Exact commands with flags (`wmill script preview <path> -d '<args>'`, `generate-metadata --dry-run`, `rehash`, `resource-type list --schema`) and two complete, copy-paste-ready C# examples cover the common cases. It falls short of anchor 5 because the C# section never shows how resource-typed parameters are declared in C# — only TypeScript `RT.C<Name>` and Python `c_<name>` TypedDict forms appear.

4 / 5

Workflow Clarity

A clear intent-based decision workflow with explicit validation checkpoints: preview validates before any deploy, `--dry-run` lists stale items before narrowing with a path, and the regenerated `.lock` must be diffed with version bumps reported to the user. Deploy is explicitly gated on user request. Not anchor 5: steps are not laid out as an ordered sequence and there is no error-recovery guidance when preview fails.

4 / 5

Progressive Disclosure

Headers are clear and in-file navigation is easy, but no bundle files exist while the language-agnostic "Windmill Script Writing Guide" (General Principles, Return Values, Preprocessor Scripts) is inlined — content that belongs in a shared reference since it is duplicated across the language family. References to `AGENTS.wmill.md` are external to the bundle. This matches anchor 3's 'content that should be separate is inline'.

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 provides a clear, imperative trigger ('MUST use when writing C# scripts') but completely omits what the skill does, and its trigger coverage is a single phrase with no synonyms or Windmill scoping. It is functional as a trigger yet far below the quality of the good examples, which state capabilities and multiple trigger conditions.

Suggestions

State what the skill does before the trigger, e.g. "Write and test Windmill C# scripts: `Main` entrypoint signature, `#r` NuGet references, `wmill script preview` and `generate-metadata` workflow. Use when writing, editing, or testing C# scripts (.cs) in a Windmill workspace."

Add natural trigger synonyms and variations — C#, CSharp, .NET, dotnet — alongside "C# scripts" so keyword coverage reaches anchor 4-5.

Scope the trigger to Windmill to reduce conflict risk with general C# coding requests and sibling language skills.

DimensionReasoningScore

Specificity

"MUST use when writing C# scripts" names the domain but states no concrete capability of the skill — it never says what the skill does (Windmill script structure, preview/metadata commands, NuGet handling). It clears anchor 1 because the domain is named, but lacks even the 1-2 concrete actions anchor 3 requires.

2 / 5

Completeness

The 'when' is explicit ("MUST use when writing C# scripts") but the 'what' is entirely absent — the skill's capabilities are never described. This is the anchor-2 pattern ('only when is present without what'), matching the example 'Use when working with documents'.

2 / 5

Trigger Term Quality

"writing C# scripts" is exactly the natural phrase a user would say, but it is the only trigger phrase; synonyms and variations (C#, CSharp, .NET, dotnet, Windmill scripts) are missing. This matches 'some relevant keywords but missing common variations', not the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"C# scripts" is a fairly distinct niche, but without 'Windmill' scoping the description can over-trigger on any general C# coding request and overlaps the sibling write-script-* family by design. It sits between anchors 3 and 4; the unscoped trigger keeps it at 3.

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