Chatbot Builder — manage Chatbot Builder data via the Membrane CLI

Prerequisites: network access and a Membrane account (a free tier is supported — no paid plan required); the Membrane CLI (`npm install -g @membranehq/cli@latest`) Install "Chatbot Builder — manage Chatbot Builder data via the Membrane CLI" for me. It gives my agent @membranedev's integration workflow: install the Membrane CLI, log in (browser auth or the headless authorization-code flow), ensure a connection to Chatbot Builder, discover and run actions in natural language (list/get/create/update/delete opportunities, pipelines, contacts, tags, flows; send flows and text messages), and fall back to direct API proxy requests when no action covers the use case. IMPORTANT: the license terms were not verifiable (no verifiable license in the fetched file) — fetch from the link only, reproduce nothing beyond the link, and read the repo's license terms yourself before reuse. License note: the skill's frontmatter claims MIT but the catalog manifest records the license as unknown — manifest takes precedence. Repository: https://github.com/membranedev/application-skills/blob/main/skills/chatbot-builder/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, credentials only via the secure vault (Membrane handles auth server-side; never paste API keys in chat). 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 "chatbot-builder". 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. install the Membrane CLI, create a Membrane account and complete `membrane login`; nothing else — Membrane manages credentials server-side). 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.