Polly
v1.0.2Polly integration. Manage Organizations. Use when the user wants to interact with Polly data.
⭐ 0· 98·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/description (Polly integration) aligns with the instructions which use the Membrane CLI to connect to Polly and run actions or proxy requests. No unrelated services, env vars, or binaries are requested.
Instruction Scope
SKILL.md confines runtime actions to installing and using the @membranehq/cli, running membrane commands to list/connect/run actions and proxy requests. The instructions do not ask the agent to read unrelated local files or exfiltrate data. They do require network access and a Membrane account (declared).
Install Mechanism
There is no embedded install spec in the package (instruction-only). The doc recommends installing the Membrane CLI via npm (-g). This is a common approach; the installer is user-invoked and not embedded in the skill. Users should still verify the npm package and maintainer before a global install.
Credentials
The skill declares no required env vars or credentials and explicitly recommends using Membrane connections rather than asking for API keys. The requested permissions (network + Membrane account) are proportionate to a third-party API integration.
Persistence & Privilege
Skill is instruction-only, always:false, and does not request persistent presence or modify other skills/config. It relies on the external Membrane service for auth and does not store credentials locally.
Assessment
This skill is an instruction-only wrapper that tells the agent to use the Membrane CLI to interact with Polly. Before installing/using it: (1) verify the @membranehq/cli npm package and maintainer if you will run a global npm install; (2) understand that using the skill means granting Membrane a connector-level connection to your Polly workspace (review Membrane's privacy, access, and token handling); (3) use the provided connection flow rather than pasting API keys into chat; and (4) if you operate in a locked-down environment, confirm you are allowed to install global npm packages and open browser-based auth flows.Like a lobster shell, security has layers — review code before you run it.
latestvk977mzvq9w45qgjdcw5j1dbyks8423db
License
MIT-0
Free to use, modify, and redistribute. No attribution required.