Helpspace

v1.0.2

Helpspace integration. Manage Organizations. Use when the user wants to interact with Helpspace data.

0· 92·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill purpose (Helpspace integration) aligns with the runtime instructions (use Membrane CLI to connect, list actions, run actions, and proxy requests). However, the package metadata lists no required binaries while the instructions require npm and the membrane CLI — a minor mismatch in declared requirements.
Instruction Scope
SKILL.md stays on-topic: it instructs the agent to install and use the Membrane CLI to manage connections and call Helpspace APIs (including a proxy mode). It does not ask the agent to read unrelated files, environment variables, or transmit data to unknown endpoints beyond Membrane/Helpspace.
Install Mechanism
There is no registry-level install spec; the README tells users to run `npm install -g @membranehq/cli`. Installing a global npm CLI is a common pattern and the package name appears to match the vendor, but the installer step is not declared in the skill metadata and requires npm to be present.
Credentials
The skill declares no environment variables or secrets. Authentication is delegated to Membrane (the flow uses `membrane login` and browser-based auth). That is proportionate to the stated purpose — the skill does not request unrelated credentials.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide changes or other skills' configs. It relies on the Membrane CLI and an account, and allows normal autonomous invocation (platform default).
Assessment
This skill uses the Membrane CLI to talk to Helpspace and does not request extra environment secrets in the skill metadata. Before installing: (1) confirm you are comfortable running a global npm install and that npm is available on the target machine; (2) verify the @membranehq/cli npm package and its repository (trust the publisher); (3) understand that Membrane will hold the Helpspace credentials and the skill will be able to make API calls via your Membrane connection — ensure the account you connect with has appropriate permissions; (4) the registry metadata did not list npm/membrane as required binaries — treat that as a minor inconsistency and verify install steps manually. If you need higher assurance, inspect the npm package source or use a controlled environment to install and test the CLI first.

Like a lobster shell, security has layers — review code before you run it.

latestvk970jm3e2kp7e780t69jp9qaxh842qsk

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments