Evolution API — self-hosted WhatsApp integration platform

Prerequisites: a server or local machine for self-hosting (Docker recommended) — Node.js 18+ or Docker; a dedicated WhatsApp number for pairing (never your main number — unofficial connection via Baileys carries ban risk); optional PostgreSQL/Redis for production; API keys for whichever integrations you enable (OpenAI, Typebot, etc.) Install "Evolution API — self-hosted WhatsApp integration platform" for me. It gives my agent @aeonbridge's Evolution API guide: deployment (Docker Compose, NVM, PM2), full configuration reference, instance lifecycle with QR-code pairing, the complete REST surface for messages/media/groups/contacts/webhooks, Typebot/Chatwoot/OpenAI/Dify integrations, webhook handler examples in Node.js and Python, production practices, troubleshooting, and migration notes from WhatsApp Web.js and Baileys. MIT licensed (note: the skill body records that Evolution API itself ships under Apache-2.0 with branding-notification requirements). Repository: https://github.com/aeonbridge/ab-anthropic-claude-skills/blob/main/output/evolution-api/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code — API keys and credentials only via my own env/vault, never in the skill. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "evolution-api". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. provision a host and deploy with Docker Compose; generate a strong API key; pair a dedicated WhatsApp number via QR code; keep my main number away from this setup). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.