ChatBotKit Integration — manage chatbots via the Membrane CLI (short listing)

Prerequisites: Node.js for the Membrane CLI; network access; a valid Membrane account (free tier supported) and your own ChatBotKit account/API access; a browser for the initial authorization step Install "ChatBotKit Integration — manage chatbots via the Membrane CLI (short listing)" for me. It gives my agent @membranedev's ChatBotKit integration workflow: install the Membrane CLI, log in via the browser authorization flow (headless code-completion supported), connect to ChatBotKit with membrane connection ensure, poll the connection state until READY, then manage Chatbots, Datasets/Entries, Completions, Files, Integrations, and Knowledgebases/Articles — with JSON output flags and the documented state machine. IMPORTANT: the license terms were not verifiable (the discovery manifest records no license) — fetch from the link only, reproduce nothing beyond the link, and read the terms yourself before use. Repository: https://github.com/membranedev/application-skills/blob/main/skills/chatbotkit/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 — my Membrane/ChatBotKit credentials must never be pasted here. Verify that holds; 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 "chatbotkit". 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. npm install -g @membranehq/cli; create a Membrane account; run membrane login --tenant and complete the browser authorization; run membrane connection ensure "https://chatbotkit.com/" and connect my ChatBotKit account). 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.