Eightfold
v1.0.0Eightfold integration. Manage data, records, and automate workflows. Use when the user wants to interact with Eightfold data.
⭐ 0· 30·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
Name and description match the instructions: the SKILL.md consistently describes integrating with Eightfold via the Membrane CLI. All required actions (creating a Membrane connection, listing/running actions, proxying requests) are appropriate for an Eightfold integration.
Instruction Scope
Instructions are scoped to installing and using the Membrane CLI and do not attempt to read unrelated files or environment variables. One important caveat: the skill explicitly recommends using Membrane's proxy (membrane request), which will route arbitrary API calls (and their payloads) through Membrane's servers — this is expected for the stated design but has privacy/PII implications when working with HR data.
Install Mechanism
There is no platform install spec in the registry (instruction-only), so nothing is installed automatically by the platform. The SKILL.md tells the user to run `npm install -g @membranehq/cli` — a standard public npm package. This is appropriate for the skill but users should verify the npm package and publisher before installing.
Credentials
The skill declares no required environment variables or credentials and instructs users to authenticate via Membrane's login flow (browser-based). That matches the claim that Membrane manages auth server-side and avoids asking for local API keys. No unrelated secrets are requested.
Persistence & Privilege
Flags show normal privileges (always: false, agent-invocable allowed). The skill does not request persistent presence or elevated platform-wide configuration changes.
Assessment
This skill appears to do what it claims: it instructs the agent to use the Membrane CLI to connect to Eightfold. Before proceeding: (1) confirm you trust the @membranehq/cli npm package (publisher, package integrity, and version); (2) understand that using Membrane's proxy will send Eightfold data (potentially sensitive HR/PII) through Membrane's servers — verify your organization's data-sharing policy and Membrane's privacy/security posture; (3) when possible, limit requests to the minimum data needed and prefer pre-built actions that avoid sending raw sensitive payloads; (4) if you require offline or direct API access, consider a workflow that does not route sensitive records through a third party.Like a lobster shell, security has layers — review code before you run it.
latestvk9709dztd24s9qwmd7m7c9at8n847cyr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.