Name: ansible
Rating: 55.2 (1 reviews)
Author: membranedev

ansible

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

Quality

62%

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 content is a solid, executable Membrane/Ansible CLI guide with a real validation feedback loop in the connection workflow. Its main weaknesses are an unnecessary introductory explanation of Ansible and a broken 'Step 2' cross-reference under an odd '1b' heading.

Suggestions

Remove the opening paragraph defining Ansible and its audience; Claude already knows this, and it wastes context tokens.

Fix the broken 'Step 2' reference and normalize the '1b' heading into a coherent numbered sequence (1, 2, 3...) so the connection workflow is unambiguous.

Add one worked end-to-end example (e.g. connect, discover an action with a real intent, run it) so the 'Popular actions' section is copy-paste ready rather than restating discovery.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening paragraph explains what Ansible is and who uses it ('Ansible is an open-source automation tool used for configuration management...') — concepts Claude already knows — and the 'Ansible Overview' bullet list plus 'Use action names and parameters as needed' add little. This matches 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests with a flag table. It is not a 5 because examples rely on placeholders (CONNECTION_ID, QUERY) and the 'Popular actions' section duplicates discovery guidance without a worked example.	4 / 5
Workflow Clarity	The connection workflow is sequenced with a validation feedback loop (poll --wait, branch on state, re-poll after CLIENT_ACTION_REQUIRED, surface error on CONFIGURATION_ERROR/SETUP_FAILED). It is not a 5 because it references a non-existent 'Step 2' and uses an unexplained '1b' heading, leaving minor navigation gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Working with Ansible, Popular actions, Best practices) with no nested or buried references and only one external docs link, appropriate for a single-file integration skill. It is not a 5 because the thin Overview section and the broken 'Step 2' reference slightly reduce navigability.	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 has an explicit Use-when trigger and a distinct Ansible niche, but its capability statement is generic ('Manage data, records, and automate workflows') and trigger-term coverage is thin. Specificity and trigger terms are the main weaknesses.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Ansible actions, e.g. 'List and run Ansible playbooks, manage inventories and credentials, and check job execution status.'

Expand trigger terms to natural phrases users say, e.g. 'Use when the user wants to run Ansible playbooks, manage inventories, check job status, or interact with Ansible/Tower/AWX automation.'

Tighten the 'what' so it distinguishes Ansible automation from generic data/records management.

Dimension	Reasoning	Score
Specificity	It names the Ansible domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete operations; 'manage data, records' is essentially abstract. This is below the 3 anchor, which requires 1-2 genuinely concrete actions.	2 / 5
Completeness	It states a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Ansible data'), so both are present with an explicit trigger clause. It is not a 5 because the 'what' is vague and the 'when' lacks concrete trigger phrases beyond 'interact with Ansible data'.	4 / 5
Trigger Term Quality	The only natural keyword is 'Ansible' (in 'interact with Ansible data'); it is relevant but missing common variations, synonyms, or file extensions, matching the 'some relevant keywords but missing variations' anchor. It is not a 4 because coverage is limited to a single domain term.	3 / 5
Distinctiveness Conflict Risk	'Ansible integration' is a clear, specific niche with a distinct trigger unlikely to fire for unrelated skills. It is not a 5 because the broad 'Manage data, records, and automate workflows' phrasing leaves minor overlap risk with general automation or data-management skills.	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
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

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.