Ansible Role Creator - Auto-activating skill for DevOps Advanced. Triggers on: ansible role creator, ansible role creator Part of the DevOps Advanced skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ansible-role-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting primarily of metadata rather than actionable content. It fails to describe what the skill actually does, provides redundant and limited trigger terms, and lacks any 'Use when...' guidance. The only slight positive is that 'Ansible' provides some domain specificity.
Suggestions
Add specific capabilities: 'Creates Ansible role directory structures with tasks, handlers, defaults, vars, templates, and meta files. Generates molecule test configurations and README documentation.'
Add a 'Use when...' clause: 'Use when the user wants to create a new Ansible role, scaffold role structure, generate role templates, or set up automation playbooks.'
Expand trigger terms to include natural variations: 'ansible role', 'create role', 'new ansible role', 'role scaffold', 'role template', 'playbook role', 'infrastructure automation role'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Ansible Role Creator') without describing any concrete actions. There are no specific capabilities listed like 'creates role directory structures', 'generates tasks/handlers/defaults files', or 'scaffolds molecule tests'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger phrase. There is no 'Use when...' clause or explicit trigger guidance explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('ansible role creator' listed twice) and overly specific. Missing natural variations users would say like 'create ansible role', 'new role', 'scaffold role', 'role template', or 'ansible playbook structure'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Ansible Role Creator' is somewhat specific to a niche (Ansible automation), which reduces conflict with general skills. However, it could overlap with broader DevOps or infrastructure-as-code skills due to lack of specific differentiating details. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no substantive guidance. It describes what an Ansible role creator skill might do but provides absolutely no actionable information about how to actually create Ansible roles - no directory structure, no example tasks/handlers/defaults, no molecule testing, no best practices for role design.
Suggestions
Add the standard Ansible role directory structure with explanation (tasks/, handlers/, defaults/, vars/, templates/, files/, meta/)
Include a concrete, executable example showing how to create a minimal role with at least one task and one handler
Add validation steps such as ansible-lint commands and molecule test initialization
Provide a workflow sequence: 1) ansible-galaxy init, 2) define defaults, 3) write tasks, 4) lint, 5) test with molecule
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for creating Ansible roles. The content only describes what the skill supposedly does without actually teaching anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Creating Ansible roles involves specific directory structures, file templates, and validation steps - none of which are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or related documentation that would help with actual Ansible role creation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Table of Contents
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.