Amazon Polly
v1.0.2Amazon Polly integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon Polly data.
⭐ 0· 71·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 (Amazon Polly integration) match the SKILL.md: it instructs using Membrane to connect to Amazon Polly, list actions, run actions, or proxy API requests. No unrelated credentials or capabilities are requested.
Instruction Scope
SKILL.md stays on-task: it tells the user/agent to install and use the Membrane CLI, authenticate via browser, create connections, list/run actions, or proxy requests to Polly. It does not instruct reading unrelated files, exfiltrating environment variables, or contacting unexpected endpoints beyond Membrane/AWS.
Install Mechanism
The manifest contains no automated install spec, but the instructions recommend installing @membranehq/cli via npm (global). Using npm is a common delivery mechanism but is a third‑party package install that writes to disk — the user should verify the package and publisher before installing globally.
Credentials
The skill declares no required env vars or credentials. Runtime instructions rely on a Membrane account and browser-based auth; the skill explicitly recommends not asking users for AWS API keys. This is proportionate to its stated function.
Persistence & Privilege
Skill flags are default (not always:true). There is no install-time behavior encoded in the manifest that would modify other skills or system settings. Autonomous invocation is allowed by default but not combined with other concerning privileges.
Assessment
This skill is coherent: it expects you to use the Membrane CLI to talk to Amazon Polly and does not ask for AWS keys. Before installing or running commands: 1) verify the Membrane project and @membranehq/cli package (check the npm page and the GitHub repository referenced) and ensure you trust that third‑party service, because Membrane will proxy requests and hold your service credentials; 2) prefer installing CLI tools from a trusted environment (consider avoiding global npm installs if you’re unsure); and 3) confirm the skill author/publisher (the registry metadata lists an owner ID and 'source: unknown') to ensure you’re comfortable granting the Membrane connection access to your Polly data.Like a lobster shell, security has layers — review code before you run it.
latestvk976fyajvp03v52m5g611r45tx842c87
License
MIT-0
Free to use, modify, and redistribute. No attribution required.