write-script-ansible

MUST use when writing Ansible playbooks.

Quality

71%

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-ansible/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured, with executable commands, complete YAML examples, clear sequencing, and validation checkpoints for editing and metadata sync. The only weakness is mild verbosity in a few explanatory passages that could be trimmed without losing clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and avoids explaining concepts Claude already knows, but a few passages are padded with explanatory restatement (e.g. 'pushing is a deploy, and deploying just to test overwrites the workspace version with untested changes') that could be tightened, fitting the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable commands (wmill script preview/run, generate-metadata --dry-run, generate-metadata rehash) and complete copy-paste YAML examples for the Windmill header and Ansible plays, with concrete placeholder syntax per language, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Multi-step processes (preview vs run vs sync push, metadata sync, post-write test offer) are clearly sequenced with explicit checkpoints such as --dry-run before running and diffing .lock files to report version bumps, providing feedback loops for error recovery as the level-3 anchor requires.	3 / 3
Progressive Disclosure	No bundle files exist, so the body is self-contained with well-organized sections; external pointers (AGENTS.wmill.md, the preview skill) are clearly signaled and one level deep with no nested reference chains, matching the well-signaled one-level-deep reference anchor.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 has a clear, distinctive trigger for Ansible playbook authoring, but it is terse: it states when to use the skill without separately articulating what concrete actions the skill performs, and it offers only one natural keyword with no variations.

Suggestions

Add the concrete actions the skill performs, e.g. 'Write, structure, and validate Windmill Ansible playbooks — define extra_vars, inventories, files, and dependencies in the Windmill header and write standard Ansible plays.'

Broaden trigger terms to include natural variations users might say, such as 'YAML playbooks', 'Ansible automation', 'Ansible roles', or 'tasks'.

Keep the explicit 'Use when...' clause but pair it with a distinct 'what' clause so both what and when are clearly answered.

Dimension	Reasoning	Score
Specificity	The description names the domain and one action ('writing Ansible playbooks') but does not list multiple concrete actions, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It includes an explicit 'when' trigger ('MUST use when writing Ansible playbooks') but the 'what does this do' is only weakly implied by the same phrase, not separately and clearly stated, so it does not reach the level-3 requirement of clearly answering both what AND when.	2 / 3
Trigger Term Quality	'Ansible playbooks' is a natural term a user would say, but no common variations (YAML, roles, tasks, automation) appear, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'Ansible playbooks' carves a clear niche unlikely to overlap with other skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 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-ansible/SKILL.md
Commit: 33d2845

Reviewed: 2 days 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.