Amazon Eks
v1.0.0Amazon EKS integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon EKS data.
⭐ 0· 55·0 current·0 all-time
byMembrane Dev@membranedev
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 (Amazon EKS integration) match the instructions: all runtime steps use the Membrane CLI to create a connector, list/run actions, or proxy requests to EKS. The skill does not request unrelated credentials or system access.
Instruction Scope
SKILL.md limits agent behavior to installing/using the Membrane CLI, logging in, creating/using a connector, listing actions, and proxying API requests. It does not instruct reading arbitrary local files or unrelated environment variables. Note: once a Membrane connection is established, the CLI/proxy can perform arbitrary EKS API calls (which is expected for this integration).
Install Mechanism
There is no platform install spec in the registry (instruction-only), but the docs tell the user to run `npm install -g @membranehq/cli` (npm registry). That's a common install path but requires network access and global npm privileges; verify package authenticity before installing globally.
Credentials
The skill declares no required env vars or credentials and the instructions explicitly tell users to rely on Membrane for auth rather than provide AWS keys locally. The SKILL.md does note a Membrane account is required (network access). This aligns with the stated purpose.
Persistence & Privilege
No install-time persistence or elevated privileges are requested. always:false and default agent invocation settings are sensible. The skill is instruction-only and does not modify other skills or system-wide configs.
Assessment
This skill is internally consistent: it uses the Membrane CLI to broker access to your EKS resources rather than asking for AWS keys. Before installing, verify the @membranehq/cli package and its source (npm author, package integrity), confirm you trust Membrane to manage credentials, and ensure the connector uses least-privilege IAM roles for any AWS access. Installing the CLI globally requires admin rights and network access—consider installing in a controlled environment or using npx for ephemeral runs. If you need stronger assurance, review Membrane's security/privacy docs and the referenced GitHub repository before connecting production clusters.Like a lobster shell, security has layers — review code before you run it.
latestvk97b1ze47d129yrfbnac83wjmn84an5r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.