CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-bash

MUST use when writing Bash 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-bash/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 concrete, executable Windmill-specific guidance with a well-gated run/preview/deploy workflow and meaningful validation checkpoints. Its weaknesses are redundancy (repeated deploy-gating and shebang rules) and a monolithic structure that mixes language-agnostic Windmill content into a Bash-specific skill.

Suggestions

State the deploy-only-when-explicitly-asked rule once and cross-reference it, instead of repeating it across the CLI commands, preview-vs-run, sync-push, and after-writing sections.

Move the cross-language general Windmill guidance (preprocessors, resource types, return values) into a shared reference file (e.g. references/windmill-general.md) and keep SKILL.md focused on Bash specifics plus a pointer.

Remove the duplicate shebang prohibition — it is stated in prose ("Do not include #!/bin/bash") and again in the Important list.

DimensionReasoningScore

Conciseness

Most content is genuinely non-obvious platform detail (lock hash invalidation, `generate-metadata rehash`, hub resource types), but the deploy-only-when-asked rule is restated four times, the shebang prohibition appears twice (line 82 and the "Important" list), and long parenthetical run-ons could be tightened. Matches anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened'); not 4 because the redundancy exceeds minor instances.

3 / 5

Actionability

Concrete commands with exact flags (`wmill script preview <script_path>`, `generate-metadata --dry-run`, `rehash`, `--strict-folder-boundaries`, `resource-type list --schema`) plus executable bash snippets with correct positional-arg and heredoc-JSON syntax. Matches anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps') — the gap being "Place scripts in a folder" naming no folder; not 5 because a few specifics like that are missing.

4 / 5

Workflow Clarity

A clear decision tree for preview vs run vs sync push with real checkpoints: dry-run before regenerating metadata, diffing regenerated locks to report version bumps, and "the preview has already validated the change" as a deploy precondition. Matches anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps'); not 5 because there is no explicit error-recovery loop when a preview or validation fails.

4 / 5

Progressive Disclosure

No bundle files exist, so everything is one inline file; headers are present, but general cross-language Windmill material (preprocessor scripts, resource types, return values, TypeScript/Python typing) sits inline in a Bash-named skill where a shared reference belongs. Matches anchor 3 ('Some structure but could be better organized; content that should be separate is inline'); not 4 because the language-general and Bash-specific material are not split, and pointers like AGENTS.wmill.md and the preview skill resolve outside the skill.

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 is effectively only a trigger clause: it says when to use the skill but not what the skill does. The domain (Bash scripts) is named concretely, but without any capability statement, platform context, or trigger synonyms it under-informs both skill selection and triggering.

Suggestions

Add a what clause with concrete capabilities, e.g. "Write Windmill Bash scripts: positional-arg inputs, JSON stdout results, resource-typed credentials. MUST use when writing Bash scripts for Windmill."

Mention Windmill (or the wmill CLI) so the skill is distinguishable from generic bash/shell-scripting skills.

Add trigger synonyms such as "shell script" or ".sh" so natural user phrasings beyond "Bash scripts" also match.

DimensionReasoningScore

Specificity

The description's only substance is "writing Bash scripts" — the domain is named concretely, but zero capability actions are stated (nothing about script structure, positional args, JSON output, or wmill commands). Matches anchor 2 ('Names the domain but actions are minimal or generic'); not 1 because the domain is specific rather than pure abstraction, not 3 because no actions at all are listed.

2 / 5

Completeness

Only the "when" is present ("MUST use when writing Bash scripts") with no "what" whatsoever — the exact case of anchor 2 ('only when is present without what'). Not 3 because the "what" is not even weakly implied; not 1 because the trigger clause is explicit and concrete.

2 / 5

Trigger Term Quality

"writing Bash scripts" is a natural phrase a user would say, but there are no synonyms or variations ("shell script", ".sh", "sh"). Matches anchor 3 ('Some relevant keywords but missing common variations or synonyms'); not 4 because coverage is a single keyword phrase.

3 / 5

Distinctiveness Conflict Risk

"writing Bash scripts" is somewhat specific, but with no mention of Windmill it would trigger on any generic bash-scripting request, overlapping with general shell-scripting guidance. Matches anchor 3 ('Somewhat specific but could still overlap with similar skills'); not 4 because the missing platform context creates real overlap risk.

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