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
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 title and category label rather than a functional skill description. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other DevOps skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Ansible playbooks, defines roles and tasks, configures inventory files, and creates YAML automation scripts for infrastructure provisioning.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Ansible, playbooks, YAML automation, configuration management, infrastructure as code, or deploying with Ansible.'
Remove the duplicated trigger term ('ansible playbook generator' is listed twice) and replace with diverse natural language variations users might actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Ansible Playbook Generator') but does not describe any concrete actions. There are no specific capabilities listed such as 'generates playbooks', 'configures roles', 'sets up inventory files', etc. It reads more like a label than a description. | 1 / 3 |
Completeness | The description barely answers 'what does this do' (generates Ansible playbooks, implied only from the name) and has no explicit 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'ansible playbook generator' repeated twice. It misses natural user phrases like 'ansible', 'playbook', 'YAML automation', 'infrastructure as code', 'ansible role', 'ansible task', 'configuration management', or 'deploy with ansible'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Ansible Playbook' does narrow the domain somewhat, making it unlikely to conflict with non-DevOps skills. However, the lack of specific actions and the vague 'DevOps Advanced' category label could cause overlap with other DevOps or infrastructure-related 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 is a hollow placeholder with no substantive content. It contains only meta-descriptions and trigger phrases but provides zero actionable guidance, no code examples, no Ansible-specific patterns, and no workflow for generating playbooks. It would be entirely useless to Claude in performing any Ansible-related task.
Suggestions
Add concrete, executable Ansible playbook YAML examples covering common use cases (e.g., provisioning a web server, deploying an application, configuring users).
Define a clear workflow for playbook generation: gather requirements → select modules → structure roles/tasks → validate with `ansible-lint` → test with `--check` mode.
Include Ansible best practices as specific, actionable rules (e.g., 'always use FQCN for modules', 'use `become: true` only at task level', 'prefer `ansible.builtin.template` over `copy` for config files').
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that provide no technical value and replace with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual Ansible playbook content, code, or specific guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no Ansible playbook examples, no YAML snippets, no commands, no specific patterns. The content only describes what it could do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any procedural guidance for generating Ansible playbooks. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no bundle files to support it. The 'Related Skills' section mentions a category but provides no links or paths. | 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
13d35b8
- 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.