Aws Well Architected
v1.0.0AWS Well-Architected integration. Manage data, records, and automate workflows. Use when the user wants to interact with AWS Well-Architected data.
⭐ 0· 30·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 name/description (AWS Well-Architected integration) matches the instructions: all runtime steps are about installing and using the Membrane CLI to connect to AWS Well‑Architected. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md stays within scope: it directs installing @membranehq/cli, performing Membrane login, creating a Membrane connection, listing/running actions, and proxying API requests through Membrane. Important: traffic and credentials are handled via Membrane (a third‑party service), so AWS workload data and API calls will transit/be managed by Membrane rather than the agent directly. The instructions do not ask the agent to read local files or other system secrets.
Install Mechanism
There is no formal install spec in the registry metadata, but the README instructs the user to install the Membrane CLI via npm (global install) or use npx. This is a standard approach (npm registry) but it does write a binary to disk and pulls code from the public npm registry; verify package authenticity and prefer npx if you want to avoid a global install.
Credentials
The skill declares no required environment variables or credentials. Instead it relies on Membrane-managed connections and browser-based auth. That is proportionate to the stated purpose, but it does mean you will grant Membrane delegated access to your AWS Well‑Architected data during the connection flow—ensure you trust the service and review the scopes requested at connect time.
Persistence & Privilege
The skill is instruction-only, has no install-time persistent agent privileges, and does not set always:true. It does not request modification of other skills or system-wide settings.
Assessment
This skill is coherent and uses the Membrane CLI to access AWS Well‑Architected. Before installing or using it: (1) verify the Membrane project/package (@membranehq/cli) on npm and consider using npx to avoid a global install; (2) review the connector/auth scopes during the Membrane connect flow—you're granting Membrane access to AWS Well‑Architected data; (3) if possible, test in a limited-permission AWS account or a sandbox workload; (4) do not paste AWS keys into the agent; follow the browser-based connector flow; and (5) review Membrane's privacy/security documentation (and their homepage/repository) to confirm you’re comfortable with a third party proxying your API calls.Like a lobster shell, security has layers — review code before you run it.
latestvk972pswme00mpb8a7941c1ah51849az9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.