Officient
v1.0.0Officient integration. Manage data, records, and automate workflows. Use when the user wants to interact with Officient data.
⭐ 0· 50·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
Name and description align with the instructions: the SKILL.md explains how to use Membrane to interact with Officient. No unrelated permissions, env vars, or tooling are requested.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Officient via Membrane. The instructions do not ask the agent to read unrelated files, environment variables, or transmit data to unexpected endpoints.
Install Mechanism
Install is a global npm install of @membranehq/cli. This is expected for a CLI-based integration but carries the usual moderate risk of installing a package from npm; the package is traceable (npm/GitHub) rather than an arbitrary URL or archive.
Credentials
The skill declares no required environment variables or credentials and relies on Membrane's browser-based login/connection flow. That matches the described behavior and is proportionate to the stated purpose.
Persistence & Privilege
The skill is instruction-only, does not request permanent presence (always:false), and does not attempt to modify other skills or system-wide configs.
Assessment
This skill is coherent: it tells the agent to use the Membrane CLI to authenticate and proxy requests to Officient rather than asking for API keys. Before installing, verify the @membranehq/cli package and its maintainer on npm/GitHub (to reduce supply-chain risk from a global npm install). Understand that connecting will open a browser-based auth flow and that Membrane will hold/manage credentials and proxy requests to Officient — review Membrane's privacy/access policies if the Officient data is sensitive. If you run in a headless or high-security environment, prefer reviewing the CLI source and confirm it meets your organization’s install policies before running npm -g install.Like a lobster shell, security has layers — review code before you run it.
latestvk97ez551h3311amqf2v4jt62g184ers6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.