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 extremely weak—it reads more like a metadata label than a functional description. It provides no concrete actions, no natural trigger terms beyond the skill name repeated, and no guidance on when Claude should select this skill. It would be nearly indistinguishable from any other Ansible-related skill in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Ansible role directory structures, creates tasks/handlers/defaults/vars files, and scaffolds molecule test configurations.'
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.'
Remove the duplicate trigger term ('ansible role creator' is listed twice) and expand with natural variations users might say, such as 'ansible role', 'create role', 'role scaffold', 'ansible directory structure'.
| 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', or any specific capabilities. | 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 or equivalent trigger guidance. | 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' is somewhat specific to a niche (Ansible roles), which reduces conflict with unrelated skills. However, the lack of detail about what it does versus other DevOps or Ansible-related skills means overlap is still possible. | 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 an empty placeholder with no actionable content whatsoever. It contains only generic meta-descriptions and trigger phrases, but provides zero technical guidance on creating Ansible roles—no directory structure, no example tasks, no commands, no validation steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable content: include the `ansible-galaxy init` command, show the resulting directory structure, and provide example task/handler/defaults YAML files for a realistic role.
Define a clear multi-step workflow with validation: e.g., 1) scaffold with `ansible-galaxy init`, 2) define variables in defaults/main.yml, 3) write tasks, 4) validate with `ansible-lint`, 5) test with `molecule test`.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical guidance.
Add progressive disclosure by referencing supporting files for advanced topics (e.g., molecule testing config, CI/CD integration, complex role patterns with Jinja2 templates).
| 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 playbook, no YAML snippets. The skill describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Creating an Ansible role is inherently a multi-step process (directory scaffolding, writing tasks/handlers/defaults/templates, testing), yet no steps, sequence, or validation checkpoints are provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to supporting files, no structured sections with real content, and no navigation to deeper material. There are no bundle files to support it either. | 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.