write-script-java

MUST use when writing Java scripts.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

67%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 content is actionable and well-structured with concrete commands and executable Java examples, supported by a clear intent-based workflow and validation guidance. Its main weakness is redundancy where the deploy/intent guidance is repeated across several sections.

Suggestions

Consolidate the repeated deploy/intent guidance (stated in the CLI bullet list, "Preview vs run", and "After writing") into a single authoritative section to reduce token cost.

Add a brief validation step for the Java example, e.g. running `wmill script preview` to confirm the script executes after writing the Main class.

Cross-link the Maven dependencies section to the metadata-sync guidance so dependency changes are clearly tied to running `wmill generate-metadata`.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence, but the deploy/intent guidance is restated across "Preview vs run", "After writing", and the CLI bullet list, adding noticeable padding that could be consolidated.	3 / 5
Actionability	Concrete executable commands (e.g. `wmill script preview <script_path>`, `wmill generate-metadata --dry-run`) and complete, copy-paste Java/Maven code examples cover the common cases with only minor gaps.	4 / 5
Workflow Clarity	The intent-based decision flow for preview vs run vs deploy is clearly sequenced with explicit gating ("Only suggest/run a deploy when the user explicitly asks") and checkpoints like diffing regenerated locks and reporting version bumps; minor validation gaps remain.	4 / 5
Progressive Disclosure	Content is organized into clear sections (CLI Commands, Java, Maven Dependencies) with one-level-deep references to `AGENTS.wmill.md` and the `preview` skill; no bundle files exist, and most content is appropriately placed inline.	4 / 5
	Total	15 / 20 Passed

Description

28%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 terse and trigger-driven but fails to state what the skill actually does, listing no concrete capabilities. It would benefit from naming the specific actions (creating a Main class, adding Maven dependencies, running wmill script commands) alongside the trigger.

Suggestions

State the concrete actions the skill performs, e.g. "Write wmill Java scripts with a Main class and Maven dependencies, then preview/generate-metadata via wmill."

Add natural trigger variations users would say, such as "Java", "Maven dependency", "wmill script", or "compile Java".

Clarify the "what" explicitly so both capability and trigger are present, e.g. "...Use when creating or editing wmill Java scripts."

Dimension	Reasoning	Score
Specificity	The phrase "writing Java scripts" names the domain but lists no concrete actions (no mention of creating Main classes, managing Maven dependencies, or running wmill commands), matching the anchor for naming the domain with minimal/generic actions.	2 / 5
Completeness	It gives a clear "when" ("MUST use when writing Java scripts") but the "what" is barely implied — no description of what the skill actually does — which fits the anchor where only the trigger is present without a real "what".	2 / 5
Trigger Term Quality	"writing Java scripts" provides only one generic keyword phrase and misses the natural variations a user would say (e.g. "Java", "Maven", "wmill script", "compile Java"), fitting the one-or-two-generic-keywords anchor.	2 / 5
Distinctiveness Conflict Risk	"writing Java scripts" is somewhat specific to this skill's niche but is generic enough to overlap with any general Java-authoring skill, matching the somewhat-specific-but-still-overlapping anchor.	3 / 5
	Total	9 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 74af4ed

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.