Helpdocs
v1.0.0HelpDocs integration. Manage data, records, and automate workflows. Use when the user wants to interact with HelpDocs data.
⭐ 0· 52·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
medium confidencePurpose & Capability
The name/description say 'HelpDocs integration' and the SKILL.md exclusively shows how to use the Membrane CLI to connect to HelpDocs, list actions, run actions, and proxy API requests. Requesting the Membrane CLI is coherent with the stated purpose.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, creating a connection, invoking actions, and proxying requests to the HelpDocs API. The instructions do not ask the agent to read unrelated files, export environment variables, or send data to unexpected endpoints.
Install Mechanism
The skill is instruction-only but tells the user to run 'npm install -g @membranehq/cli' (and uses npx in examples). Installing a global npm package will write code to disk and add a binary to PATH; the package appears to be a scoped package (@membranehq) on the npm registry which is reasonable for this use case, but installing third-party CLIs carries the usual risk and the SKILL.md does not provide a pinned release or checksum.
Credentials
The skill declares no required env vars or credentials. It explicitly instructs not to ask users for API keys and relies on Membrane to manage auth server-side, which is proportionate for a connector integration.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system settings, and is user-invocable. There is no indication of persistent or elevated privileges beyond installing a CLI if the user chooses to.
Assessment
This skill is coherent: it relies on the Membrane CLI to access HelpDocs and does not ask for unrelated secrets. Before installing or running it: (1) verify the publisher of @membranehq/cli on the npm registry (check the package page, maintainers, and recent downloads); (2) prefer using npx or a container if you want to avoid installing a global package; (3) review Membrane's privacy/security docs since Membrane will hold/handle the HelpDocs credentials and can access your HelpDocs data; (4) confirm the repository/homepage links and publisher identity if you require provenance (the skill metadata's source is 'unknown'); (5) if you are uncomfortable installing third‑party CLIs system‑wide, run the commands in an isolated environment (container or VM). Overall the skill appears to do what it says, but exercise normal caution for third‑party CLI installs and delegation of auth to an external service.Like a lobster shell, security has layers — review code before you run it.
latestvk970qshqa89r6n4wqb0b0pbey184cqzw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.