Tessl • The management layer for AI agent skills

SkillPublic

ansible

Ansible integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ansible data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ansible/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers strong, executable CLI guidance with a clear connect-then-act workflow and useful state-handling checkpoints. Its main weaknesses are a padded introductory paragraph that re-explains Ansible, an empty "Popular actions" section, and broken step references ("Step 2", "1b") from a numbering scheme that was never written.

Suggestions

Delete the opening background paragraph about what Ansible is and who uses it — Claude already knows this — and cut the filler line "Use action names and parameters as needed."

Fix the dangling references: either add an explicit "Step 2" heading and renumber the sections (1, 1b, 2, ...) or replace "skip to **Step 2**" and "#### 1b." with descriptive section links.

Populate the "Popular actions" section with 3-5 real example commands (e.g. launching a job template, listing inventories) or remove the empty header.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Ansible is an open-source automation tool used for configuration management... System administrators, DevOps engineers, and developers use Ansible...") explains background Claude already knows, and lines like "Use action names and parameters as needed." are filler. This matches anchor 3 (mostly efficient but includes unnecessary explanation) rather than 4 because the intro is a clear, removable padding block.	3 / 5
Actionability	Concrete copy-paste commands cover the main flows: CLI install, login (including headless code completion), `connection ensure`, long-poll waiting, `action list --intent`, `action run --input`, and a proxy options table. This matches anchor 4 (mostly executable, minor gaps) rather than 5 because the "Popular actions" section contains no actual examples and placeholders like CONNECTION_ID and QUERY are never concretized.	4 / 5
Workflow Clarity	The connect-then-act sequence is clear, with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop after the user completes an action. It matches anchor 4 rather than 5 because the text says "skip to Step 2" but no step numbering exists in the document — the lone "#### 1b." heading is an orphaned fragment of a numbering scheme.	4 / 5
Progressive Disclosure	The skill is a single well-sectioned file with no bundle files, and the material present (connection states, proxy flags) is workflow-relevant rather than offloadable bulk, matching anchor 4 (good structure, minor organization gaps). It is not 5 because the ~140-line body and the detailed clientAction/proxy reference material could live in a separate reference file, and the empty "Popular actions" section is a structural stub.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names the target tool and includes an explicit "Use when" clause, so both what and when are present, but the capability description is generic filler ("Manage data, records") with no concrete Ansible operations. Trigger coverage relies almost entirely on the word "Ansible" and misses natural terms like playbooks, inventory, or deployment.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Ansible operations, e.g. "Run and monitor Ansible playbooks, manage inventories and credentials, and schedule automation jobs".

Expand the when-clause with natural trigger phrases: "Use when the user mentions Ansible, playbooks, inventories, configuration management, or automation jobs".

Drop the vague phrase "interact with Ansible data", which is circular and adds no distinctiveness.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Ansible domain but the actions are generic; no concrete operations (e.g. run playbooks, manage inventories, deploy configs) are stated. It sits at anchor 2 rather than 3 because not even one specific action is named, and above 1 because the domain and purpose are identified.	2 / 5
Completeness	Both parts are explicitly present: what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Ansible data"), but the when-clause is circular and the what is vague, matching anchor 4 (both present, when could be more specific). It is not 5 because neither half is concrete, and not 3 because the when-clause is explicit rather than merely implied.	4 / 5
Trigger Term Quality	The description includes "Ansible" and "automate workflows", which are relevant, but misses the natural phrases users would say such as "playbooks", "inventory", "configuration management", or "deployment". This matches anchor 3 (some relevant keywords, missing common variations) rather than 4, since coverage beyond the tool name itself is thin.	3 / 5
Distinctiveness Conflict Risk	Naming a specific tool (Ansible) gives a clear niche with distinct triggers, matching anchor 4 (mostly distinct, minor overlap risk). It is not 5 because generic phrases like "manage data, records, and automate workflows" overlap with broad automation/DevOps skills, and not 3 because the tool name anchors it well.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/ansible/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

Discovery Implementation Validation

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.

ansible

Table of Contents

Is this your skill?