Amazon Ecs
v1.0.2Amazon ECS integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon ECS data.
⭐ 0· 73·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 match the instructions: it tells the agent to use the Membrane CLI to interact with Amazon ECS. Required capabilities (network + Membrane account) are consistent with the stated purpose.
Instruction Scope
SKILL.md confines activity to installing and using the Membrane CLI (login, connect, action list/run, proxy requests). It does allow proxying arbitrary requests to the Amazon ECS API via Membrane — which is consistent with the purpose but means the connection you create can perform wide ECS actions, so verify and limit permissions when creating the connection.
Install Mechanism
No install spec in the registry (instruction-only), but the runtime instructions tell users to run `npm install -g @membranehq/cli`. Installing a global npm package is a common but moderate-risk operation: verify the package and its publisher before installing.
Credentials
The skill does not request local environment variables or AWS keys. Instead it relies on Membrane to manage credentials server-side; this is proportionate but means you must trust Membrane with access to your AWS/ECS account and associated permissions.
Persistence & Privilege
The skill does not request always:true or system-wide config changes. It's user-invocable and can be used autonomously by the agent (platform default) but there is no evidence of excessive persistence or privilege requests.
Assessment
This skill appears internally consistent: it uses Membrane as a proxy to access ECS and does not ask for local AWS keys. Before installing/using it: 1) Verify the @membranehq/cli npm package and the publisher (check npm and the GitHub repo linked in SKILL.md). 2) Understand and limit the IAM permissions granted when you create the Membrane connection—use least-privilege roles for ECS. 3) Treat Membrane as a third party that will have access to your ECS data; review their privacy/security docs. 4) When running actions or proxy requests, inspect action IDs and input JSON before execution to avoid unintended destructive operations. 5) Avoid installing global packages from untrusted sources on production systems.Like a lobster shell, security has layers — review code before you run it.
latestvk978fpxw2pd95xwa5h59mx68qx842s12
License
MIT-0
Free to use, modify, and redistribute. No attribution required.