Ansible Convert logo

Ansible Convert

Community
realsigridjin
ansible-convert

Use when converting shell scripts to Ansible playbooks. Use when migrating bash automation, manual procedures, or Dockerfiles to idempotent Ansible tasks.

Overview

Publisherrealsigridjin
Repositoryhello-ansible-skills
Skill nameansible-convert
Stars
95
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by realsigridjin on GitHub. Read the source before you install it.

Installation

Install the Ansible Convert AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/realsigridjin/hello-ansible-skills/tree/main/skills/ansible-convert
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/realsigridjin/hello-ansible-skills.git /tmp/hello-ansible-skills
mkdir -p .claude/skills
cp -r /tmp/hello-ansible-skills/skills/ansible-convert .claude/skills/ansible-convert
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ansible Convert in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ansible Convert on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ansible Convert is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Shell to Ansible Conversion

Overview

Shell scripts execute commands imperatively; Ansible declares desired state. Conversion means rethinking operations as state declarations, not translating commands line-by-line. The goal is idempotency: running twice produces identical results.

When to Use

  • Converting existing shell scripts to playbooks
  • Migrating manual server setup procedures
  • Replacing bash automation with Ansible
  • Converting Dockerfile RUN commands

Core Principle

Don't wrap shell commands in Ansible's shell module. Find the module that achieves the same end state declaratively.

bash
# Shell: imperative
mkdir -p /opt/app
chown app:app /opt/app
yaml
# Ansible: declarative
- ansible.builtin.file:
    path: /opt/app
    state: directory
    owner: app
    group: app
    mode: '0755'

Conversion Table

Shell CommandAnsible ModuleNotes
mkdir -pansible.builtin.filestate: directory
cpansible.builtin.copyStatic files
cp with variablesansible.builtin.templateUse .j2 templates
rm -rfansible.builtin.filestate: absent
ln -sansible.builtin.filestate: link
chmod, chownInclude in file/copy/templatemode, owner, group params
apt-get installansible.builtin.aptupdate_cache: yes
yum installansible.builtin.yumOr use package for cross-platform
pip installansible.builtin.pipSpecify executable if needed
useraddansible.builtin.userHandles home, shell, groups
systemctl startansible.builtin.servicestate: started
systemctl enableansible.builtin.serviceenabled: yes
curl -Oansible.builtin.get_urlUse checksum for verification
tar -xzfansible.builtin.unarchiveremote_src: yes if already on target
echo >> fileansible.builtin.lineinfileEnsures line exists
cat > fileansible.builtin.copycontent: parameter

Control Flow Conversion

Conditionals

bash
# Shell
if [ -f /etc/debian_version ]; then
    apt-get install nginx
fi
yaml
# Ansible
- ansible.builtin.apt:
    name: nginx
  when: ansible_os_family == "Debian"

Loops

bash
# Shell
for user in alice bob; do
    useradd $user
done
yaml
# Ansible
- ansible.builtin.user:
    name: "{{ item }}"
  loop:
    - alice
    - bob

When Shell Module is Necessary

Use command or shell only when no module exists. Always add proper change detection:

yaml
- name: Run custom installer
  ansible.builtin.shell: /opt/app/install.sh
  args:
    creates: /opt/app/.installed  # Skip if file exists
  register: install_result
  changed_when: "'Installed' in install_result.stdout"
  failed_when: install_result.rc != 0 and 'already installed' not in install_result.stderr

Variable Extraction

Identify values to parameterize:

  • Version numbers → app_version: "1.2.3"
  • Paths → app_dir: "/opt/app"
  • Usernames → app_user: "appuser"
  • Ports → app_port: 8080

Place in defaults/main.yml for easy override.

Conversion Workflow

  1. Read entire script, identify major phases
  2. Map each command to Ansible module
  3. Extract hardcoded values as variables
  4. Order tasks for dependencies (dirs before files)
  5. Add handlers for service restarts
  6. Test with --check --diff
  7. Verify idempotency: second run shows no changes

Frequently asked questions

What does the Ansible Convert AI skill do?

Use when converting shell scripts to Ansible playbooks. Use when migrating bash automation, manual procedures, or Dockerfiles to idempotent Ansible tasks.

Why use Ansible Convert on TypingMind?

Because you install it once and use it with any model. Ansible Convert is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ansible Convert in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/realsigridjin/hello-ansible-skills/tree/main/skills/ansible-convert. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ansible Convert?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ansible Convert?

As many as you like. As long as a model supports skills, you can use Ansible Convert with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ansible Convert AI skill free?

Yes. It is published on GitHub by realsigridjin under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇