CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-java

MUST use when writing Java scripts.

Quality

57%

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

Quality

Content

56%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.

Strong operational guidance — the preview-vs-run-vs-deploy decision rules, metadata-sync workflow with dry-run and diff feedback loops, and the concrete Java Main-class and //requirements examples are genuinely useful. However, the body mixes large amounts of language-generic Windmill material into a Java-specific skill, is written in long dense paragraphs, and omits the Java-specific parameter/resource details its own General Principles promise.

Suggestions

Move the language-generic guidance (General Principles, Preprocessor Scripts, non-Java parameter syntax) into a shared reference file (e.g. references/general.md) referenced from this skill, keeping SKILL.md focused on Java.

Add the missing Java-specific details the body promises: how a Java script declares resource-typed parameters and how to use the Windmill client (wmill) from Java.

Compress the 'Keep metadata in sync' section into a short numbered workflow (edit → generate-metadata → diff .lock → report version changes) instead of four dense paragraphs.

DimensionReasoningScore

Conciseness

The body is noticeably verbose for a Java-specific skill: four dense paragraphs on metadata sync, and substantial content irrelevant to Java such as SQL placeholder syntax ("$1 for PostgreSQL, ? for MySQL/Snowflake, @P1 for MSSQL... positional $1, $2, … for Bash, param(...) for PowerShell"), TypeScript/Python resource patterns ("RT.C<Name> in TypeScript, a c_<name> TypedDict in Python"), and preprocessor scripts "written in TypeScript or Python". Not 3: the volume of non-Java material and run-on prose exceeds 'some unnecessary explanation'; not 1: the CLI and Java-specific material is substantive guidance, not padded explanation of concepts Claude already knows.

2 / 5

Actionability

Mostly executable guidance with concrete commands ("wmill script preview <script_path>", "wmill generate-metadata --dry-run", "wmill resource-type list --schema") and a copy-paste-ready Java example plus the //requirements Maven format. Not 5: General Principles promises "the language section below shows how that language declares parameters" and gives TypeScript/Python resource-parameter forms, but the Java section shows only plain String/int parameters — no Java resource-typed parameter or wmill-client usage.

4 / 5

Workflow Clarity

Clear decision rules and checkpoints: preview as the local validation step before deploy, "Only suggest/run a deploy when the user explicitly asks to deploy/publish/push", "--dry-run — it lists each stale item with a reason ... without changing anything", and "diff the regenerated .lock / .script.lock files and tell the user which dependency versions changed" as an explicit feedback loop. Not 5: the write → preview → generate-metadata → deploy sequence is never laid out as an ordered workflow; the reader must assemble it from dense prose.

4 / 5

Progressive Disclosure

There is real structure (## CLI Commands with ### subsections, # Java) and clearly signaled external pointers ("see the **Deploying** section in `AGENTS.wmill.md`", "use the `preview` skill"), but language-generic content (General Principles covering TypeScript/Python/SQL/Bash conventions, and the Preprocessor Scripts section) is inlined in a Java-specific skill — content that belongs in a shared reference file. Not 2: structure and navigation are present and functional; not 4: the misplaced non-Java material is more than a minor organization gap.

3 / 5

Total

13

/

20

Passed

Description

40%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 bare trigger clause: accurate, explicit, and reasonably distinctive, but it communicates zero information about what the skill actually provides. It satisfies the 'use when' requirement while omitting the 'what' entirely, which is its main weakness.

Suggestions

Add a 'what' clause, e.g. 'Conventions for Windmill scripts in Java: Main class with a public static Object main method, Maven dependencies via //requirements comments, and the wmill preview/run/metadata workflow. Use when writing or editing Java scripts for Windmill.'

Include natural trigger variations such as 'Java script', 'script in Java', and 'Windmill Java' to improve recall.

Mention Windmill explicitly to avoid conflict with generic (non-Windmill) Java coding requests.

DimensionReasoningScore

Specificity

"MUST use when writing Java scripts" names the domain (writing Java scripts) but describes no actions the skill performs — nothing about Windmill conventions, the Main class, or dependency management. Not 1: the domain is concrete, not pure abstraction as in 'Helps with documents'; not 3: there is no 'what' content at all, whereas anchor 3 expects 1-2 concrete named actions.

2 / 5

Completeness

Only the 'when' is present ("MUST use when writing Java scripts"); the 'what' is entirely absent — the description never states that the skill provides Windmill Java script conventions. This matches anchor 2 ('only when is present without what', e.g. 'Use when working with documents'). Not 3: anchor 3 requires a clear 'what', which is missing altogether, not merely weakly implied.

2 / 5

Trigger Term Quality

The keywords 'writing', 'Java', and 'scripts' match the core natural phrase a user would say ('write a Java script'). Not 4: coverage stops at the bare domain phrase — common variations and synonyms ('Java code', 'create a Java script', 'script in Java', 'Windmill', '.java') are missing, comparable in coverage to the anchor-3 example 'Works with PDF files'.

3 / 5

Distinctiveness Conflict Risk

'Java scripts' carves a clear niche distinct from sibling language skills and is unlikely to trigger for other Windmill tasks. Not 5: without mentioning Windmill, the description risks triggering on ordinary non-Windmill Java coding requests — minor overlap risk with generic Java work.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/write-script-java/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.