CtrlK
BlogDocsLog inGet started
Tessl Logo

write-script-go

MUST use when writing Go scripts.

55

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

Quality

Content

82%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, actionable skill: executable Go examples and specific wmill commands with intent-driven decision rules and useful validation checkpoints. It is concise and well-structured, with only minor trim and organization opportunities.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence, giving operational commands and Go patterns without explaining basics; only a few explanatory passages (e.g. the metadata-sync defaults) could be trimmed, matching the efficient-with-minor-trim anchor.

4 / 5

Actionability

It provides fully executable, copy-paste-ready Go code (package inner, main signature, struct returns, error handling) and specific wmill CLI commands covering the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The write → preview/run → generate-metadata → deploy flow is sequenced with intent-based decision rules and checkpoints (--dry-run, lock diffing, version-bump reporting), with only minor gaps in a formal validate-fix-retry loop, matching the clear-sequence-with-most-checkpoints anchor.

4 / 5

Progressive Disclosure

Content is well-organized under clear headers (CLI Commands, Go: Structure/Return Types/Error Handling) with signaled external pointers (AGENTS.wmill.md, the preview skill); the two-topic split and ~109-line length leave minor organization gaps versus a clean one-level reference structure.

4 / 5

Total

17

/

20

Passed

Description

41%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 trigger ("when writing Go scripts") but entirely omits what the skill does, leaving its purpose opaque. It is concise and uses a natural trigger phrase but is not distinctive without the Windmill context.

Suggestions

Add a 'what' clause stating what the skill does, e.g. "Generates Windmill Go scripts with the required inner package and main signature, then previews and syncs metadata."

Include the Windmill/tooling context and synonyms (Golang, .go, Windmill script) to improve distinctiveness and trigger-term coverage.

State concrete actions (write, preview, generate-metadata, deploy) so the description answers both 'what' and 'when' explicitly.

DimensionReasoningScore

Specificity

The phrase "writing Go scripts" names the domain (Go) and one concrete action (writing), matching the anchor for naming a domain with 1-2 actions but not comprehensive coverage.

3 / 5

Completeness

Only the 'when' is present ("MUST use when writing Go scripts") with no 'what' describing what the skill actually does, matching the anchor where only 'when' is present without 'what'.

2 / 5

Trigger Term Quality

"writing Go scripts" is a natural phrase a user would say, but coverage is thin with no synonyms or variations (e.g. Golang, .go, Windmill), matching the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"writing Go scripts" is somewhat specific to Go but could overlap with generic Go-authoring skills and lacks the Windmill context that would make it distinct, matching the anchor for somewhat specific but still overlapping.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
windmill-labs/windmill
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.