ansible-good-practices
v2.2.1Review Ansible code against Red Hat CoP automation good practices. Use when the user wants to audit, lint, review, check, or validate Ansible roles, playbooks, collections, or inventory for compliance with CoP rules. Optionally validates module parameters via ansible-know MCP. Use when user says "lint my role", "check my playbook", "review best practices", or "audit my Ansible code". Do NOT use for general Python or YAML linting unrelated to Ansible. Do NOT use for answering Ansible module usage questions or checking syntax against official Ansible documentation (use ansible-docs instead).
28 GitHub starsUpdated 8 hours ago
Directory evidence
- Runtimes
- Claude Code and Agent Plugins
- Parsed components
- 2 skill or MCP entries
- Source updated
- Aug 20, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install ansible-good-practices@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/leogallego/claude-ansible-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is ansible-good-practices/.
Plugin files
├── .claude-plugin/plugin.json├── plugin.json├── skills/ansible-good-practices/SKILL.md└── .mcp.json
Included Skills1
Review Ansible code against Red Hat CoP automation good practices. Use when the user wants to audit, lint, review, check, or validate Ansible roles, playbooks, collections, or inventory for compliance with CoP rules. Optionally validates module parameters via ansible-know MCP. Use when user says "lint my role", "check my playbook", "review best practices", or "audit my Ansible code". Do NOT use for general Python or YAML linting unrelated to Ansible. Do NOT use for answering Ansible module usage questions or checking syntax against official Ansible documentation (use ansible-docs instead).
MCP servers1
- command
- uvx
- args
- ansible-know-mcp
Plugin manifests2
{
"name": "ansible-good-practices",
"version": "2.2.1",
"description": "Review Ansible code against Red Hat CoP automation good practices. Use when the user wants to audit, lint, review, check, or validate Ansible roles, playbooks, collections, or inventory for compliance with CoP rules. Optionally validates module parameters via ansible-know MCP. Use when user says \"lint my role\", \"check my playbook\", \"review best practices\", or \"audit my Ansible code\". Do NOT use for general Python or YAML linting unrelated to Ansible. Do NOT use for answering Ansible module usage questions or checking syntax against official Ansible documentation (use ansible-docs instead)."
}{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "ansible-good-practices",
"version": "2.2.1",
"description": "Review Ansible code against Red Hat CoP automation good practices.",
"author": {
"name": "leogallego"
},
"license": "GPL-3.0-or-later",
"keywords": [
"ansible",
"ansible-good-practices",
"good-practices",
"automation",
"review"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[ansible-good-practices on Agent Plugins Marketplace](https://pluginsmp.com/plugins/ansible-good-practices)