Amazon Elasticsearch
v1.0.0Amazon Elasticsearch integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon Elasticsearch data.
⭐ 0· 60·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
medium confidencePurpose & Capability
The name and description claim an Amazon Elasticsearch integration and the SKILL.md consistently instructs use of the Membrane CLI to connect, discover actions, and proxy requests to Amazon Elasticsearch. Requiring a Membrane account and using Membrane to hold credentials is coherent with this purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, performing login, creating connections, listing actions, running actions, and proxying requests. There are no instructions to read unrelated local files, access unrelated environment variables, or exfiltrate data outside of the Membrane/AWS flow.
Install Mechanism
The skill is instruction-only (no install spec), but it directs users to install and run @membranehq/cli via npm -g and npx. Installing or executing packages from npm means executing third-party code fetched at install/run time — this is expected for a CLI integration but is a runtime risk the user should accept consciously.
Credentials
The skill does not request local AWS credentials or environment variables and delegates auth to Membrane, which is proportionate to the stated goal. However, this places trust in Membrane (a third-party service) to store and manage your Elasticsearch/AWS credentials and to proxy requests.
Persistence & Privilege
The skill does not request persistent privileges (always:false), does not modify other skills or system-wide settings in the instructions, and is user-invocable. Autonomous invocation is allowed by default but not specifically privileged here.
Assessment
This skill appears internally consistent: it uses Membrane as a proxy to avoid asking for AWS keys directly. Before installing or using it, verify the Membrane project (homepage and GitHub repo), understand that membrane login will give Membrane access to your Elasticsearch/AWS resources, and be cautious about running npm -g or npx (these fetch and execute remote code). If you need to keep credentials off third-party services, this skill's design (delegating auth to Membrane) may not be appropriate. Review the Membrane CLI source and consider installing the CLI in a controlled environment rather than globally if you have security concerns.Like a lobster shell, security has layers — review code before you run it.
latestvk971ssp2nz62fk4dtpmr9yznas84d1f7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.