Feedier
v1.0.2Feedier integration. Manage Surveys, Integrations, Users. Use when the user wants to interact with Feedier data.
⭐ 0· 115·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 name/description (Feedier integration) matches the instructions: all runtime steps use the Membrane CLI to connect to Feedier and run actions. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs the agent to install and run the Membrane CLI, perform interactive login (opens a browser or uses a headless login flow), list/create connections, run actions, and proxy requests through Membrane. This stays within the stated purpose but means requests and credentials are proxied via the Membrane service — a privacy/trust consideration for sensitive data.
Install Mechanism
There is no packaged install spec in the registry; the guide tells users to run `npm install -g @membranehq/cli`. Installing a global npm CLI is expected for this use case but executes third-party code on the host, so verify the package and publisher before installing.
Credentials
The skill declares no required environment variables or config paths. The instructions rely on Membrane-managed auth rather than asking for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is instruction-only, does not request persistent 'always' inclusion, and does not modify other skill or system configurations. Normal agent invocation/autonomy settings are used.
Assessment
This skill is coherent: it uses the Membrane CLI to access Feedier and does not ask for unrelated secrets. Before installing: (1) verify the npm package @membranehq/cli is the official publisher (check the package page and the repository), (2) understand that requests and auth are proxied through Membrane servers (so avoid sending highly sensitive data unless you trust the service), and (3) consider installing the CLI in a controlled environment (container or VM) if you want to limit exposure. Do not supply Feedier API keys manually—use the connection flow as instructed.Like a lobster shell, security has layers — review code before you run it.
latestvk97cp1hvt9t3qhxv8cc5abjd75843v56
License
MIT-0
Free to use, modify, and redistribute. No attribution required.