Originalityai
v1.0.2Originality.ai integration. Manage Documents, Users, Workspaces. Use when the user wants to interact with Originality.ai data.
⭐ 0· 82·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
medium confidencePurpose & Capability
The name/description (Originality.ai integration) matches the instructions: all actions are performed via the Membrane CLI and the steps (login, create connection, list actions, run actions, proxy requests) are what you'd expect for a connector-based integration.
Instruction Scope
Instructions stay within the stated purpose (discover and call Originality.ai endpoints through Membrane). Note: the SKILL.md explicitly tells the agent/user to install and run the Membrane CLI and to use Membrane's proxy — which means requests and Originality.ai credentials will be handled by Membrane and data will transit their service. There are no instructions to read unrelated files or env vars.
Install Mechanism
There is no registry install spec, but the README instructs installing @membranehq/cli via npm (global). Installing a global npm CLI is a common pattern but executes third‑party code on the host; this is proportionate to the skill's described usage but users should verify the package/source before installing.
Credentials
The skill declares no required environment variables or credentials and the instructions explicitly say to let Membrane handle secrets. That aligns with an integration that delegates auth to a proxy service.
Persistence & Privilege
The skill does not request always:true and has no install-time persistence in the repo (instruction-only). It requires interactive login via Membrane but does not ask to modify other skills or system-wide configs.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to talk to Originality.ai. Before installing/using it: 1) Understand that Membrane is a third‑party proxy — Originality.ai credentials and any content you send will transit Membrane's service; review their privacy/security docs and trustworthiness. 2) Verify the npm package @membranehq/cli (owner, repository, recent activity) before running npm install -g, and avoid installing global packages from untrusted sources. 3) The skill avoids asking for local API keys (good); complete authentication through the Membrane login flow rather than pasting keys into chat. 4) If you cannot or do not want your content to flow through a proxy, do not use this skill and instead integrate Directly with Originality.ai using your own API keys. If you want a higher-assurance review, provide the skill's repository or the exact npm package metadata so it can be audited.Like a lobster shell, security has layers — review code before you run it.
latestvk97fje08xrhkdzsnvywz4v6xex842xxj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.