Icims
v1.0.2iCIMS integration. Manage data, records, and automate workflows. Use when the user wants to interact with iCIMS data.
⭐ 0· 104·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 declares an iCIMS integration and all runtime instructions use the Membrane CLI to discover actions, create connections, run actions, or proxy requests to iCIMS. There are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, logging in, creating a connector/connection, discovering actions, running actions, and proxying raw API calls. Important note: proxying and connector creation routes iCIMS API calls (and any data you send) through Membrane's servers — this is expected for a proxy-based integration but is a privacy/third-party-data-flow consideration.
Install Mechanism
This is an instruction-only skill (no install spec in the registry), but it tells the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal way to obtain a CLI but requires trusting the npm package and publisher. The skill itself does not automatically install anything.
Credentials
The skill requests no local environment variables or config paths. It relies on the Membrane account and browser-based login/connector flows to obtain and manage credentials, which is proportionate to an integration that proxies requests and manages auth server-side.
Persistence & Privilege
The skill does not request always: true and does not modify other skills or system-wide settings. It relies on Membrane-managed connections (which will persist on Membrane's side) — expected for a connector.
Assessment
This skill appears coherent, but before installing or using it: (1) verify the authenticity of the @membranehq/cli package on npm and the Membrane service (homepage, repo, publisher), (2) review what OAuth scopes or permissions will be granted when you 'connect' iCIMS to Membrane and whether you are comfortable routing data through Membrane's servers, (3) avoid installing global npm packages unless you trust the publisher or inspect the package, (4) for sensitive environments consider running the CLI from an isolated machine or container and confirm how long Membrane retains connection credentials and data and how to revoke access if needed.Like a lobster shell, security has layers — review code before you run it.
latestvk975btw9jqcac6sw0nrbdt91558422kv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.