creating-ansible-playbooks

Execute use when you need to work with Ansible automation. This skill provides Ansible playbook creation with comprehensive guidance and automation. Trigger with phrases like "create Ansible playbook", "automate with Ansible", or "configure with Ansible".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

77%Weight 40%Scale 1-3

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

A well-structured, concise instruction body with strong workflow sequencing and validation, weakened only by the absence of a complete executable playbook example and by failing to link the bundled scripts, templates, and reference material.

Suggestions

Add a minimal complete, copy-paste-ready playbook YAML example (hosts, become, vars, tasks, handlers) so the core artifact is fully executable rather than only described.

Link the existing bundle files from the body, e.g. 'See scripts/validate_playbook.py for validation' and 'Use assets/playbook_template.yml as a starting template', to surface one-level-deep references.

Reference assets/validation_rules.yml and scripts/secure_playbook.py from the relevant Instructions steps so the security and validation tooling is discoverable.

Dimension	Reasoning	Score
Conciseness	The body is lean with no conceptual padding, each instruction a single tight line, and it assumes Claude's competence without explaining what Ansible is or how it works.	3 / 3
Actionability	Concrete commands and directory layouts appear throughout (ansible-lint, ansible-playbook --check --diff, tasks/handlers/templates), but there is no complete executable playbook YAML example of the core artifact, leaving a key detail missing.	2 / 3
Workflow Clarity	A clearly sequenced 9-step list includes explicit validation checkpoints (ansible-lint, --check --diff dry run, idempotency test) and an Error Handling table provides error-to-fix feedback loops.	3 / 3
Progressive Disclosure	The body is well-organized into clear sections, but it never references or links the provided bundle files (scripts/validate_playbook.py, assets/playbook_template.yml, references/), so available supporting material is not signaled.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid description with an explicit trigger clause and natural user phrasing, though it names only one concrete action and leans on buzzword padding rather than a comprehensive capability list.

Suggestions

Replace 'comprehensive guidance and automation' with additional concrete actions (e.g., create roles, write inventory files, validate with ansible-lint) to broaden the specificity of capabilities.

Expand the trigger phrases to cover more natural variations users might say, such as 'write a role' or 'set up inventory'.

Dimension	Reasoning	Score
Specificity	Only one concrete action ('Ansible playbook creation') is named, padded with buzzword fluff ('comprehensive guidance and automation'), so it names a domain and one action but is not a comprehensive list.	2 / 3
Completeness	It answers both 'what' (Ansible playbook creation) and 'when' via an explicit trigger clause ('Trigger with phrases like...'), matching the what-and-when anchor.	3 / 3
Trigger Term Quality	Three natural user phrases are provided ('create Ansible playbook', 'automate with Ansible', 'configure with Ansible'), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It targets a clear niche (Ansible automation) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/ansible-playbook-creator/skills/creating-ansible-playbooks/SKILL.md
Commit: c4eafaf

Reviewed: 5 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.