Eyepopai
v1.0.2EyePop.ai integration. Manage data, records, and automate workflows. Use when the user wants to interact with EyePop.ai data.
⭐ 0· 86·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's name and description (EyePop.ai integration) match the instructions (using Membrane to call EyePop.ai). Minor inconsistency: the SKILL.md instructs installing the Membrane CLI via npm, but the registry metadata lists no required binaries (npm/membrane). This is coherent with the purpose but the metadata omission is worth noting.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating a connection, listing actions, running actions, or proxying requests to EyePop.ai via Membrane. The instructions do not direct the agent to read arbitrary local files, harvest unrelated environment variables, or send data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but SKILL.md asks users to run `npm install -g @membranehq/cli` (and examples using npx). Installing an npm package globally writes binaries to disk; the package is a namespaced npm package (@membranehq) which is typical, but users should verify the package's authenticity on the npm registry before installing.
Credentials
The skill declares no required env vars or credentials and explicitly recommends using Membrane-managed connections rather than asking users for API keys. The requested scope is proportional to the stated purpose (integrating with EyePop.ai through Membrane).
Persistence & Privilege
always:false and no special persistence or cross-skill configuration are requested. The skill is user-invocable and can be run autonomously by the agent (platform default), which is expected for integrations of this type.
Assessment
This skill is coherent with its stated purpose, but before installing or running it: (1) verify the @membranehq/cli package on the npm registry (publisher, download counts, repo), since SKILL.md asks you to install it globally; (2) understand that authentication uses browser-based OAuth and that Membrane will proxy requests to EyePop.ai—so data and requests will flow through Membrane's service (review their privacy/security docs and the OAuth consent scopes shown at login); (3) consider installing the CLI in a controlled environment (container or virtualenv) rather than system-wide; (4) the registry metadata omitted required binaries (npm/membrane) — ensure you have npm and trust the CLI before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk975a9qgb5e88whwvd5xs82c7n843xnj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.