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 boilerplate auto-generated stub with no meaningful content. It lacks concrete actions, natural trigger terms, and any explicit guidance on when Claude should select this skill. The only redeeming quality is that 'Ansible Playbook' is a somewhat distinctive domain keyword.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Ansible playbooks, creates roles and tasks, configures inventory files, and writes YAML automation scripts.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create or edit Ansible playbooks, write automation tasks, configure infrastructure with Ansible, or mentions YAML playbooks, roles, or inventory files.'
Remove the duplicated trigger term and replace with diverse natural language variations users might actually say, such as 'ansible automation', 'write a playbook', 'ansible role', 'infrastructure automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Ansible Playbook Generator') but provides no concrete actions. It does not describe what the skill actually does—no mention of generating, editing, validating playbooks, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not 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 'create ansible playbook', 'write playbook', 'ansible automation', 'YAML playbook', 'ansible role', 'infrastructure as code', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Ansible Playbook' is fairly specific to a niche domain, which reduces conflict risk with unrelated skills. However, the lack of detail about what it does versus other DevOps skills means it could still overlap with general DevOps or infrastructure-as-code 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 essentially a placeholder with no substantive content. It contains no Ansible-specific knowledge, no playbook examples, no YAML templates, no commands, and no actionable guidance whatsoever. It repeatedly restates that it helps with 'ansible playbook generator' without ever demonstrating how.
Suggestions
Add concrete Ansible playbook YAML examples (e.g., a production-ready playbook for common tasks like provisioning a web server or deploying an application) with copy-paste ready code.
Include a clear workflow for playbook generation: define inventory → write playbook → validate with `ansible-lint` → dry-run with `--check` → execute, with explicit validation checkpoints.
Remove all the meta-description sections (Purpose, When to Use, Example Triggers, Capabilities) and replace them with actual Ansible best practices, directory structure conventions (roles, handlers, vars), and common patterns.
Add references to supplementary files for advanced topics like Ansible Vault, dynamic inventory, custom modules, or role-based organization.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or configurations related to Ansible playbook generation. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No Ansible playbook examples, no YAML snippets, no commands, no specific patterns or best practices. The content only describes what it could do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The bullet point 'Provides step-by-step guidance' is an empty promise with no actual steps provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered content organization, and the sections are redundant rather than progressively informative. | 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
c8a915c
- 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.