ansible-runner

Execute Ansible playbooks via MCP ansible_navigator with RBAC failure reruns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill ansible-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ansible-runner
Source: https://github.com/spigell/my-agents/tree/main/.agents/skills/ansible-runner
Command: npx skills add https://github.com/spigell/my-agents --skill ansible-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably run Ansible playbooks through the MCP ansible_navigator tool while identifying RBAC/permission failures precisely, so you can request the exact access updates and rerun safely.

Core Features & Use Cases

  • MCP-first execution: Runs playbooks using the MCP ansible_navigator execution path and passes the user’s original request as userMessage, with sensible defaults like mode: "stdout" and disableExecutionEnvironment: true (unless overridden).
  • Playbook selection matrix: Uses curated playbook paths for common scenarios (deploy, workbench-only, MCP servers only) and supports explicit filePath when parser-derived paths are wrong or ambiguous.
  • Strict RBAC retry loop: On failure, extracts the failing task context (task name, file/line, error text), detects permission-related denials, requests the permission update from the developer (without guessing), and reruns only after confirmation.

Quick Start

Ask the AI to run the default RBAC-safe Ansible workflow for the workbench deploy playbook and report the recap plus any RBAC denial details.

Frequently Asked Questions about ansible-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Ansible playbooks through MCP and figure out why they fail?

You can run Ansible playbooks through the MCP ansible_navigator tool to execute deployment scenarios. When a run fails, the system extracts the failing task context and pinpoints exact permission errors to request precise access updates.

What is the best way to handle Kubernetes RBAC denials during Ansible playbook execution?

Handling Kubernetes RBAC denials requires extracting the denied subject, verb, resource, and scope from the failure logs. The system then requests the specific permission update from the developer and performs a strict confirmation loop before retrying.

How do I execute specific deployment or workbench playbooks when the path is ambiguous?

You can execute specific deployment or workbench playbooks using a curated selection matrix of paths. When parser-derived paths are wrong or ambiguous, you can provide an explicit filePath to bypass the default selection.

Can I run ansible_navigator playbooks with custom execution environments instead of stdout mode?

You can run ansible_navigator playbooks with custom execution environments by overriding the defaults. The system uses mode stdout and disableExecutionEnvironment true by default, but these can be overridden to suit your specific runtime needs.

Why does my Ansible playbook retry loop keep failing on Kubernetes permission errors?

An Ansible playbook retry loop fails when permission errors are not explicitly resolved before rerunning. The system enforces a strict developer-confirmed retry loop, ensuring the exact RBAC denial is fixed rather than guessing or blindly retrying.

Do I need to manually parse recap reports after running an MCP Ansible workflow?

You do not need to manually parse recap reports after running an MCP Ansible workflow. The system automatically requires and generates recap reporting alongside extracting any RBAC denial details for your review.