Integry
v1.0.0Integry integration. Manage data, records, and automate workflows. Use when the user wants to interact with Integry data.
⭐ 0· 62·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
medium confidencePurpose & Capability
The skill's name/description (Integry integration) matches the instructions which use the Membrane CLI to create connections, list actions, run actions, and proxy requests to Integry. Asking the user to use Membrane to handle auth is coherent with the stated purpose.
Instruction Scope
SKILL.md confines runtime actions to installing and using the @membranehq/cli and the membrane commands (login, connect, action list/run, request). It does not instruct reading unrelated files or collecting extra credentials and explicitly advises not to ask the user for API keys.
Install Mechanism
Installation instructions recommend npm install -g @membranehq/cli (and npx usage). Installing a CLI from the public npm registry is a reasonable approach here but carries the usual npm-package risk; the skill is instruction-only and does not embed or download arbitrary code itself.
Credentials
No environment variables, credentials, or config paths are required by the skill metadata. The SKILL.md relies on Membrane to manage auth and explicitly says not to ask users for API keys. One minor mismatch: the SKILL.md expects npm/npx and the membrane CLI to be available (or installable), but the skill metadata lists no required binaries.
Persistence & Privilege
The skill is not always-enabled and uses the default model-invocation behavior. It does not request persistent system-wide privileges or attempt to modify other skills or system configuration.
Assessment
This skill is an instruction-only wrapper that tells the agent to install and use @membranehq/cli to operate on Integry via Membrane. Before installing/use: (1) confirm you trust the @membranehq/cli npm package and its publisher (verify the package on npm and the linked GitHub repo), (2) be aware npm install -g modifies your system environment and requires node/npm; consider using npx for one-off runs if you don't want a global install, (3) Membrane will handle credentials server-side — confirm you are comfortable granting the Membrane service access to your Integry account during the OAuth flow, and (4) avoid running the CLI in environments with highly sensitive local credentials unless you audit the CLI source. The only small inconsistency is that the skill metadata doesn't list npm/membrane as required binaries even though the instructions assume them; that's not a fatal issue but worth noting.Like a lobster shell, security has layers — review code before you run it.
latestvk972cg69s2tastp6g82wpc4nws84b086
License
MIT-0
Free to use, modify, and redistribute. No attribution required.