ansible-playbook-generator
Ansible Playbook Generator - Auto-activating skill for DevOps Advanced. Triggers on: ansible playbook generator, ansible playbook generator Part of the DevOps Advanced skill category.
34
Quality
3%
Does it follow best practices?
Impact
86%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/ansible-playbook-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any concrete capability descriptions, and provides no guidance on when Claude should select this skill. The description reads more like metadata than actionable guidance.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Ansible playbooks for server configuration, application deployment, and infrastructure automation. Creates tasks, handlers, roles, and inventory files.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks about Ansible, playbooks, YAML automation, server provisioning, configuration management, or infrastructure as code.'
Include common file extensions and related terms users might mention: '.yml playbooks', 'ansible-playbook', 'inventory files', 'roles', 'tasks', 'handlers'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Ansible Playbook Generator') without describing any concrete actions. It lacks specifics like 'creates playbooks', 'configures hosts', 'defines tasks', or any actual capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' clause just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('ansible playbook generator' repeated twice) and overly specific. Missing natural variations users would say like 'ansible', 'playbook', 'automation', 'infrastructure as code', 'yaml config', or 'server configuration'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Ansible Playbook' provides some specificity that distinguishes it from generic DevOps skills, but the lack of concrete actions and the vague 'DevOps Advanced' category could cause overlap with other infrastructure automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is entirely generic boilerplate with no actionable guidance for Ansible playbook generation. It lacks any concrete examples, code snippets, playbook structures, or workflows. The content could apply to virtually any topic by swapping the phrase 'ansible playbook generator' with any other skill name.
Suggestions
Add executable Ansible playbook examples showing common patterns (e.g., package installation, service management, file templating)
Include a clear workflow for playbook creation: define inventory, write tasks, validate with --check, run playbook, verify results
Provide specific guidance on playbook structure (hosts, vars, tasks, handlers) with concrete YAML examples
Remove generic capability descriptions and replace with actionable best practices (e.g., idempotency patterns, role organization, variable precedence)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Ansible playbooks. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually create an Ansible playbook. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only lists vague capabilities without any sequence of actions or validation checkpoints for creating playbooks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no structure pointing to detailed materials, examples, or reference documentation. No useful navigation or organization exists. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
994edc4
- 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.