playbook-creator

Create Ansible playbooks following Red Hat CoP Type-Function patterns.

5|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/stoleas/ansible-skills --skill playbook-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-creator
Source: https://github.com/stoleas/ansible-skills/tree/main/skills/playbook-creator
Command: npx skills add https://github.com/stoleas/ansible-skills --skill playbook-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and enforces CoP-aligned Ansible playbook patterns to reduce drafting time and ensure consistency across projects.

Core Features & Use Cases

  • Type-Function pattern guidance: organizes playbooks into Type, Function, and Component levels.
  • Playbook structure templates: provides guidance for Type, Landscape, and Simple playbooks.
  • Validation-ready outputs: ensures YAML formatting, role inclusion, and tagging best practices for maintainability.

Quick Start

Create a type playbook for a web_server that installs base Linux, configures web services, and deploys a sample application.

Frequently Asked Questions about playbook-creator

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

FAQPage Schema
How do I create production-ready Ansible playbooks that follow Red Hat CoP patterns?

You can create production-ready Ansible playbooks by applying Red Hat CoP Type-Function patterns, which organize automation into Type, Function, and Component levels to ensure consistent, scalable infrastructure configuration.

What is the Type-Function pattern in Ansible automation?

The Type-Function pattern in Ansible automation organizes playbooks into Type, Landscape, and Simple structures, ensuring role inclusion and tagging best practices align with inventory-driven configuration and idempotent practices.

How do I structure an Ansible playbook for inventory-driven configuration?

Structure an Ansible playbook for inventory-driven configuration by using standard templates that separate Type, Function, and Component levels, ensuring YAML formatting and role inclusion maintain idempotent practices across your infrastructure.

Does this approach ensure Ansible playbooks are idempotent and validation-ready?

Yes, this approach ensures Ansible playbooks are idempotent and validation-ready by enforcing YAML formatting, role inclusion, and tagging best practices, resulting in maintainable outputs aligned with standard CoP templates.

What's the best way to scaffold a new Ansible automation project?

The best way to scaffold a new Ansible automation project is using standard templates that apply Type-Function pattern guidance, reducing drafting time and enforcing consistency across infrastructure projects requiring scalable automation.