What problem does it solve? On-premises Wazuh exposes three separate APIs with different ports, credentials, and auth models, plus manager configuration that only exists in ossec.conf over SSH, making even routine tasks like searching alerts or adding a Slack integration error-prone without deep platform knowledge. ## Core Features & Use Cases - Unified API client: A Python helper handles JWT auth with automatic renewal, pagination, self-signed TLS, and OpenSearch queries against the Server API (55000), Indexer API (9200), and Dashboard saved-objects API (443). - Dashboards-as-code: Export and import Wazuh UI dashboards as ndjson for backup, migration, and version control, or aggregate alert data for standalone HTML reports. - Safe ossec.conf editing over SSH: Backup, diff, XML validation, config test, and automatic rollback when adding Slack/PagerDuty integrations, active-response runbooks, or Office 365 and Cloudflare log feeds. - Use Case: Ask to list all active agents, pull the last 24 hours of level-10+ alerts, then wire a PagerDuty integration for critical rules — the skill picks the right API, authenticates, and previews every change before applying it. ## Quick Start Connect to my Wazuh server and show me all high-severity alerts from the last 24 hours grouped by agent.