Gitbook
v1.0.0GitBook integration. Manage data, records, and automate workflows. Use when the user wants to interact with GitBook data.
⭐ 0· 50·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is described as a GitBook integration and the SKILL.md consistently instructs the agent/user to use the Membrane CLI to connect to GitBook and run actions or proxy API requests. The homepage and repository references point to Membrane (an integration proxy), which matches the instructions — asking for GitBook API keys is intentionally avoided because Membrane handles auth.
Instruction Scope
The instructions are limited to installing and using the Membrane CLI, creating/connectin connections, discovering actions, running actions, and proxying requests to GitBook. They do direct the user/agent to open browser-based auth flows and to send arbitrary proxied requests via Membrane (membrane request), which is expected for a general-purpose integration but is powerful: proxied requests can access or modify any endpoint the connected account permits. The instructions do not ask to read local files or unrelated credentials.
Install Mechanism
This is an instruction-only skill (no install spec in the registry), but SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm CLI is a common pattern and the package appears to be the expected integration tool, but global npm installs write executables to disk and you should verify the package and its source (npm page and GitHub repo) before installing.
Credentials
The skill declares no required environment variables, credentials, or config paths. The SKILL.md explicitly recommends letting Membrane manage credentials instead of asking for API keys locally, which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always:true or any special persistence privileges. It is user-invocable and allows normal autonomous invocation (platform default). It does not instruct modifying other skills or system-wide agent settings.
Assessment
This skill appears internally consistent and uses the Membrane CLI as an integration layer for GitBook. Before installing or using it: 1) verify the @membranehq/cli package and its GitHub repository (confirm publisher, recent releases, and source code) rather than blindly running a global npm install; 2) understand that Membrane will proxy requests and manage auth — GitBook data will be routed through Membrane's service, so review their privacy/terms and the permissions granted during connection; 3) be cautious when using `membrane request` to call arbitrary endpoints because it can read/modify any resources the connected account permits; and 4) prefer testing in a limited/isolated account or environment first. If you need the skill to avoid any third-party routing, request or build a direct GitBook integration instead.Like a lobster shell, security has layers — review code before you run it.
latestvk973q8ynsmmyv8k2m4rfbx989h84ej3s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.