ansible-role-creator
Ansible Role Creator - Auto-activating skill for DevOps Advanced. Triggers on: ansible role creator, ansible role creator Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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-role-creator/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 with no substantive content. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Ansible role directory structures, creates tasks/handlers/defaults/vars files, and scaffolds molecule tests for role validation.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create an Ansible role, scaffold role directories, generate role templates, or set up Ansible Galaxy-compatible roles.'
Include natural keyword variations users might say, such as 'ansible role', 'role scaffold', 'ansible directory structure', 'molecule testing', 'ansible galaxy', 'role template'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Ansible Role Creator') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'creates', 'generates', 'configures', etc. It reads as a label rather than a capability description. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause—only a category label and a redundant trigger phrase. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'ansible role creator' repeated twice. There are no natural variations a user might say, such as 'create ansible role', 'ansible playbook', 'role template', 'ansible galaxy', or 'infrastructure automation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Ansible Role Creator' does narrow the domain somewhat, distinguishing it from generic DevOps skills. However, without specific actions or clear triggers, it could overlap with other Ansible-related or DevOps skills in the same category. | 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 actionable content. It repeatedly references 'ansible role creator' without ever explaining what an Ansible role structure looks like, how to create one, or providing any code, commands, or concrete guidance. It fails on every dimension by offering only abstract meta-descriptions of what the skill could do rather than actually doing it.
Suggestions
Add concrete, executable content: include the `ansible-galaxy init` command, show the standard role directory structure (tasks/, handlers/, templates/, defaults/, vars/, meta/), and provide a minimal working example of a role's main.yml.
Define a clear workflow: e.g., 1) Initialize role with `ansible-galaxy init role_name`, 2) Define variables in defaults/main.yml, 3) Write tasks in tasks/main.yml, 4) Validate with `ansible-lint`, 5) Test with `molecule test`.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical guidance and code examples.
Add a quick-start section with a complete, copy-paste-ready example role and reference files for advanced patterns (e.g., molecule testing, role dependencies, Ansible Galaxy publishing).
| 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 technical content. Every section restates the same vague idea ('ansible role creator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no Ansible role directory structure, no example playbooks, no templates. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The content merely states it can provide 'step-by-step guidance' without actually including any steps. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no quick-start section with real content, and no navigation to deeper resources. The sections are all meta-descriptions rather than organized technical content. | 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
3e83543
- 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.