creating-ansible-playbooks

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

57%

Overall

Validation — 81%

Implementation — 20%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

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

	Total	13 / 16 Passed

Implementation

20%

This skill is a generic template that provides no Ansible-specific value. It lacks any actual playbook examples, YAML syntax, module references, or concrete Ansible commands. The content could describe any software development process and fails to teach Claude anything about Ansible automation.

Suggestions

Add concrete Ansible playbook examples with actual YAML syntax showing common patterns (package installation, service management, file templating)

Include specific Ansible commands for validation: `ansible-playbook --syntax-check`, `ansible-lint`, `ansible-playbook --check` (dry run)

Replace generic process steps with Ansible-specific workflow: inventory setup, variable organization, role structure, handler usage

Remove all generic software development advice and focus only on Ansible-specific knowledge Claude wouldn't already have

Dimension	Reasoning	Score
Conciseness	Extremely verbose and generic content that explains nothing Ansible-specific. The entire document reads like a template with placeholder text that could apply to any automation task, wasting tokens on obvious process steps Claude already knows.	1 / 3
Actionability	No concrete Ansible code, no playbook examples, no YAML syntax, no specific modules or commands. Instructions like 'Execute implementation in non-production environment first' are completely abstract and provide zero executable guidance for creating Ansible playbooks.	1 / 3
Workflow Clarity	Steps are numbered and sequenced, but they're generic software development lifecycle steps, not Ansible-specific workflows. No validation commands for playbook syntax (ansible-lint, --check mode), no specific checkpoints for Ansible operations.	2 / 3
Progressive Disclosure	References external files in a structured way (templates, docs, examples directories), but the main content is a wall of generic text. The referenced files appear to be placeholders rather than real resources, and the 'Overview' and 'Examples' sections at the end are empty stubs.	2 / 3
	Total	6 / 12 Passed

Activation

90%

This description effectively communicates when to use the skill with explicit trigger phrases and clearly identifies its Ansible-specific niche. However, the capabilities section is somewhat vague ('comprehensive guidance and automation') and could benefit from listing specific concrete actions the skill enables beyond just playbook creation.

Suggestions

Expand the capabilities to list specific concrete actions like 'create playbooks, manage inventory files, configure roles, handle variables and templates, debug automation tasks'

Replace vague phrase 'comprehensive guidance and automation' with specific deliverables the skill produces

Dimension	Reasoning	Score
Specificity	Names the domain (Ansible automation) and mentions 'playbook creation' as an action, but lacks comprehensive concrete actions like 'manage inventory', 'configure roles', or 'deploy infrastructure'.	2 / 3
Completeness	Explicitly answers both what ('Ansible playbook creation with comprehensive guidance and automation') and when ('Trigger with phrases like...' provides explicit trigger guidance).	3 / 3
Trigger Term Quality	Includes natural trigger phrases users would say: 'create Ansible playbook', 'automate with Ansible', 'configure with Ansible'. These are realistic user requests.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on Ansible automation with distinct triggers mentioning 'Ansible' explicitly. Unlikely to conflict with other automation or configuration management skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.