Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Inventory Manager

ASecurity

Organizes Ansible inventory files, manages host groups, and configures dynamic inventory. Use when organizing Ansible inventory, managing host groups, or setting up dynamic inventory sources.

29 stars
0 votes
0 copies
6 views
Added 12/21/2025
devopspythonbashawsazuredatabase

Security Analysis

A100/100

Scanned 2/12/2026

$npx -y skills add armanzeroeight/fastagent-plugins --skill inventory-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Inventory Manager?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Inventory Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/armanzeroeight-inventory-manager/badge)](https://www.skillsdirectory.com/skills/armanzeroeight-inventory-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: inventory-manager
description: Organizes Ansible inventory files, manages host groups, and configures dynamic inventory. Use when organizing Ansible inventory, managing host groups, or setting up dynamic inventory sources.
---

# Inventory Manager

## Quick Start

Organize Ansible inventory with proper host groups, variables, and dynamic inventory sources.

## Instructions

### Step 1: Create static inventory

**INI format:**
```ini
# inventory/production
[webservers]
web1 ansible_host=192.168.1.10
web2 ansible_host=192.168.1.11

[databases]
db1 ansible_host=192.168.1.20
db2 ansible_host=192.168.1.21

[loadbalancers]
lb1 ansible_host=192.168.1.30

[production:children]
webservers
databases
loadbalancers

[production:vars]
ansible_user=deploy
ansible_python_interpreter=/usr/bin/python3
environment=production
```

**YAML format:**
```yaml
# inventory/production.yml
all:
  children:
    production:
      children:
        webservers:
          hosts:
            web1:
              ansible_host: 192.168.1.10
            web2:
              ansible_host: 192.168.1.11
        databases:
          hosts:
            db1:
              ansible_host: 192.168.1.20
            db2:
              ansible_host: 192.168.1.21
        loadbalancers:
          hosts:
            lb1:
              ansible_host: 192.168.1.30
      vars:
        ansible_user: deploy
        environment: production
```

### Step 2: Organize group variables

**Directory structure:**
```
inventory/
├── production
├── staging
├── group_vars/
│   ├── all.yml
│   ├── webservers.yml
│   ├── databases.yml
│   └── production.yml
└── host_vars/
    ├── web1.yml
    └── db1.yml
```

**group_vars/all.yml:**
```yaml
---
# Variables for all hosts
ansible_python_interpreter: /usr/bin/python3
ntp_servers:
  - 0.pool.ntp.org
  - 1.pool.ntp.org
```

**group_vars/webservers.yml:**
```yaml
---
# Variables for webservers group
nginx_port: 80
nginx_worker_processes: 4
app_directory: /var/www/app
```

**group_vars/production.yml:**
```yaml
---
# Variables for production environment
environment: production
backup_enabled: true
monitoring_enabled: true
```

### Step 3: Configure host-specific variables

**host_vars/web1.yml:**
```yaml
---
nginx_worker_connections: 1024
server_id: 1
```

### Step 4: Use inventory in playbooks

```bash
# Run playbook with specific inventory
ansible-playbook -i inventory/production site.yml

# Target specific group
ansible-playbook -i inventory/production site.yml --limit webservers

# Target specific host
ansible-playbook -i inventory/production site.yml --limit web1
```

## Dynamic Inventory

### AWS EC2 Plugin

**inventory/aws_ec2.yml:**
```yaml
---
plugin: amazon.aws.aws_ec2
regions:
  - us-east-1
  - us-west-2

filters:
  tag:Environment: production
  instance-state-name: running

keyed_groups:
  - key: tags.Role
    prefix: role
  - key: tags.Environment
    prefix: env
  - key: placement.availability_zone
    prefix: az

hostnames:
  - tag:Name
  - private-ip-address

compose:
  ansible_host: private_ip_address
```

### Azure Plugin

**inventory/azure_rm.yml:**
```yaml
---
plugin: azure.azcollection.azure_rm
include_vm_resource_groups:
  - production-rg

keyed_groups:
  - key: tags.role
    prefix: role
  - key: tags.environment
    prefix: env

conditional_groups:
  webservers: "'web' in tags.role"
  databases: "'db' in tags.role"
```

### Custom Script

**inventory/custom.py:**
```python
#!/usr/bin/env python3
import json

inventory = {
    "webservers": {
        "hosts": ["web1", "web2"],
        "vars": {
            "nginx_port": 80
        }
    },
    "databases": {
        "hosts": ["db1", "db2"]
    },
    "_meta": {
        "hostvars": {
            "web1": {"ansible_host": "192.168.1.10"},
            "web2": {"ansible_host": "192.168.1.11"},
            "db1": {"ansible_host": "192.168.1.20"},
            "db2": {"ansible_host": "192.168.1.21"}
        }
    }
}

print(json.dumps(inventory))
```

## Inventory Patterns

**All hosts:**
```bash
ansible all -i inventory/production -m ping
```

**Specific group:**
```bash
ansible webservers -i inventory/production -m ping
```

**Multiple groups:**
```bash
ansible 'webservers:databases' -i inventory/production -m ping
```

**Exclude group:**
```bash
ansible 'all:!databases' -i inventory/production -m ping
```

**Intersection:**
```bash
ansible 'webservers:&production' -i inventory/production -m ping
```

**Regex:**
```bash
ansible '~web.*' -i inventory/production -m ping
```

## Multi-Environment Setup

```
inventory/
├── production/
│   ├── hosts
│   ├── group_vars/
│   │   ├── all.yml
│   │   └── webservers.yml
│   └── host_vars/
├── staging/
│   ├── hosts
│   ├── group_vars/
│   │   ├── all.yml
│   │   └── webservers.yml
│   └── host_vars/
└── development/
    ├── hosts
    └── group_vars/
        └── all.yml
```

**Usage:**
```bash
# Production
ansible-playbook -i inventory/production site.yml

# Staging
ansible-playbook -i inventory/staging site.yml

# Development
ansible-playbook -i inventory/development site.yml
```

## Best Practices

1. Organize inventory by environment
2. Use group_vars for shared configuration
3. Use host_vars for host-specific settings
4. Document inventory structure
5. Use dynamic inventory for cloud resources
6. Keep sensitive data in Ansible Vault
7. Use meaningful group names
8. Implement proper variable precedence

Attribution

armanzeroeightarmanzeroeight
View sourceSee grades on GitHubMore from armanzeroeight →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Terraform Module Library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

401991 votes

sematext-otel

Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.

01 votes

Deployment Patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

2699140 votes

Babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

971540 votes

V7 Roster

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

953190 votes
View all in devops →