Jumpcloud
v1.0.0JumpCloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with JumpCloud data.
⭐ 0· 43·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
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name and description claim JumpCloud integration and all runtime instructions are about using the Membrane CLI to interact with JumpCloud resources. Requested actions (create connection, list actions, proxy requests) align with that purpose.
Instruction Scope
SKILL.md confines the agent to using the Membrane CLI and the Membrane proxy to call JumpCloud APIs. It does not instruct reading unrelated files, environment variables, or external endpoints beyond Membrane/JumpCloud. It explicitly advises not to collect API keys locally.
Install Mechanism
The skill is instruction-only (no install spec), but the SKILL.md tells the user to run `npm install -g @membranehq/cli` or use `npx`. That is a reasonable, common install path but it is not reflected in the skill's declared requirements. Installing a global npm package has normal operational risk (privileges, supply-chain), so users should prefer vetted package sources or npx.
Credentials
No environment variables or credentials are requested by the skill. The instructions explicitly rely on Membrane to manage credentials server-side and tell users not to provide local API keys, which is proportional to the described functionality.
Persistence & Privilege
The skill does not request always-on presence and uses normal, user-invocable behavior. It does not ask to modify other skills or system-wide agent settings.
Assessment
This skill is coherent: it expects you to install and use the Membrane CLI to create a JumpCloud connector and proxy API calls through Membrane, which will hold and refresh credentials. Before installing, confirm you trust the Membrane project (review https://getmembrane.com and the referenced repo) because Membrane will mediate access to your JumpCloud data. Be aware that SKILL.md recommends a global npm install; you can use `npx` to avoid a global install. When creating the connector, scope its permissions minimally (least privilege). If you prefer not to delegate credentials to a third party, consider using JumpCloud’s official API directly with your own audited tooling. Finally, note the minor metadata mismatch: the skill manifest lists no required binaries even though the instructions require the Membrane CLI and npm — this is not dangerous but worth being aware of.Like a lobster shell, security has layers — review code before you run it.
latestvk971869yqwr23g47jqhk76ztgn84e1he
License
MIT-0
Free to use, modify, and redistribute. No attribution required.