CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-go

MUST use when writing Go scripts.

Quality

64%

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

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 is a strong, highly actionable reference: exact wmill commands, decision rules keyed to user intent, and complete Go examples make it copy-paste executable. Its weaknesses are repetition (deploy-gating and 'not a deploy' stated multiple times) and multi-language scope creep that pads a nominally Go-only skill, plus no guidance on handling preview failures.

Suggestions

Consolidate the deploy-gating rule and the 'generate-metadata is not a deploy' caveat into a single statement each — they are currently repeated across three to four sections.

Move the non-Go language guidance (SQL placeholder syntax, Bash/PowerShell args, TypeScript/Python preprocessor typing) into a referenced file or trim it, since the skill is declared as Go-only.

Add a short error-recovery step for `wmill script preview` failures (read the error, fix, re-preview) to complete the feedback loop.

DimensionReasoningScore

Conciseness

Most content is dense, genuinely non-obvious Windmill platform knowledge (lock hashes, preview vs run semantics, rehash), but there is noticeable repetition — "not a deploy" is stated three times (lines 14, 31, 33) and deploy-gating is repeated four times (lines 15, 19, 26, 45) — plus scope creep: a Go-titled skill carries multi-language guidance (SQL placeholders, Bash/PowerShell args, TS/Python preprocessors). This lands between anchor 2's 'several unnecessary explanations' and anchor 4's 'minor instances of over-explanation'; it is mostly useful material that could be meaningfully tightened.

3 / 5

Actionability

The body gives exact commands with flags (`wmill script preview <script_path>`, `wmill generate-metadata rehash`, `wmill generate-metadata --dry-run`, `wmill resource-type list --schema`) and three complete, executable Go code samples including the required `package inner` declaration, return types, and error handling. Concrete cases are covered (e.g. the `requests 2.31.0 → 2.32.0` version-bump example), matching 'Fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

The write → preview → generate-metadata → deploy sequence is governed by explicit intent-based decision rules ('If the user says run/try/test with local edits, use script preview') and includes validation checkpoints: --dry-run to inspect stale items before regenerating, and diffing regenerated locks to catch version bumps before deploy. It falls short of anchor 5 only because there is no error-recovery guidance for when a preview fails, and the sequence is spread across thematic sections rather than presented as one ordered flow.

4 / 5

Progressive Disclosure

With no bundle files, the single ~130-line document is well-organized into clearly headed sections (CLI Commands, General Principles, Return Values, Preprocessors, Go) with clearly signaled external pointers (the **Deploying** section in `AGENTS.wmill.md`, the `preview` skill) that are one level deep, not nested. Anchor 4 ('Good structure; most content is appropriately placed; minor organization gaps') fits — the non-Go language guidance inlined in a Go skill is the main content that arguably belongs elsewhere.

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 minimal to a fault: it has a clear trigger ('when writing Go scripts') but says nothing about what the skill does, and it never mentions Windmill or the wmill CLI it governs. A user (or Claude) reading only this line cannot distinguish it from a generic Go-coding skill.

Suggestions

State what the skill does, e.g. 'Conventions for writing Windmill scripts in Go: inner package structure, main signature, and the wmill CLI workflow (preview, generate-metadata, deploy)'.

Add trigger variations and the platform name — 'Use when writing or editing Go scripts for Windmill, generating .script.yaml/lock metadata, or running wmill script preview' — so it does not collide with ordinary Go development.

Include natural synonyms such as 'golang' and '.go files' to improve trigger term coverage.

DimensionReasoningScore

Specificity

"MUST use when writing Go scripts" names the domain (Go scripts) but offers only a single generic action ("writing") with no concrete capabilities listed. It matches the anchor 'Names the domain but actions are minimal or generic' and falls short of anchor 3, which requires 1-2 concrete actions such as what the skill actually governs (package structure, wmill CLI usage, metadata sync).

2 / 5

Completeness

The description provides an explicit 'when' ("MUST use when writing Go scripts") but entirely omits the 'what' — it never states that the skill covers Windmill script conventions, the wmill CLI workflow, or Go packaging rules. This matches anchor 2 ('only when is present without what') and cannot reach anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"writing Go scripts" is a phrase users would naturally say, giving some relevant keywords ("Go", "script", "writing"), but coverage is thin — no "golang", no "Windmill", no ".go" file extension. This sits at 'Some relevant keywords but missing common variations or synonyms' rather than anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Go scripts" is somewhat specific, but without mentioning Windmill the description would fire on virtually any Go coding request, overlapping with general Go-development skills. Anchor 3 ('Somewhat specific but could still overlap with similar skills') is the best fit; anchor 4 would require a clearer niche such as naming the Windmill platform.

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