Poper
v1.0.0Poper integration. Manage data, records, and automate workflows. Use when the user wants to interact with Poper data.
⭐ 0· 30·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/description (Poper integration) match the SKILL.md: all actions are about using the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Poper. There are no unrelated dependencies, credentials, or filesystem paths requested.
Instruction Scope
The SKILL.md instructs running the Membrane CLI (login, connect, action list/run, request proxy). All instructions stay within the scope of interacting with Poper via Membrane; they do not instruct reading arbitrary local files, harvesting unrelated environment variables, or exfiltrating data to unknown endpoints.
Install Mechanism
The skill is instruction-only (no install spec). It recommends installing @membranehq/cli via 'npm install -g', which is an external, user-executed operation. This is expected for a CLI-based integration but carries the usual npm/global-install supply-chain and system-modification considerations — verify the package and publisher before installing.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The SKILL.md explicitly advises using Membrane to avoid asking users for API keys. Requested access (browser-based Membrane login and connector OAuth flows) is proportional to the integration.
Persistence & Privilege
Flags: always=false and model invocation defaults are normal. The skill does not request persistent system presence or modify other skills' configs. It relies on Membrane for server-side credential management, which centralizes privileges but is coherent with the stated design.
Assessment
This skill is coherent: it simply documents using the Membrane CLI to connect to Poper. Before proceeding, verify the authenticity of the @membranehq/cli package (publisher, npm page, and repository), understand that Membrane (the third-party service) will mediate and therefore have access to Poper data and tokens, and be aware that installing the CLI globally modifies your system PATH. If you prefer not to install global npm packages, run the CLI via npx or containerized tooling. No unexpected environment variables or file reads are requested by the skill itself.Like a lobster shell, security has layers — review code before you run it.
latestvk97bqfvm8t8vkt5shwjcgpsphd844c2z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.