Amentum Aerospace
v1.0.2Amentum Aerospace integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amentum Aerospace data.
⭐ 0· 113·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 skill says it integrates with Amentum Aerospace and all runtime steps use the Membrane CLI to discover connectors, create connections, list/run actions, or proxy arbitrary API calls. Required capabilities (network access, Membrane account/CLI) match the described integration.
Instruction Scope
SKILL.md instructs the agent/user to install and use the Membrane CLI, run discovery and action commands, and optionally proxy requests. It does not ask the agent to read unrelated files, environment variables, or exfiltrate secrets, and keeps scope limited to interacting with the service via Membrane.
Install Mechanism
The registry contains no automated install, but SKILL.md recommends installing @membranehq/cli globally via npm (npm install -g). This is a reasonable, common install path but does introduce the usual risks of installing a global npm package; verify the package and publisher before installing.
Credentials
The skill declares no required env vars or credentials and explicitly says Membrane handles authentication and that you should not provide API keys. Nothing requests unrelated credentials or system config.
Persistence & Privilege
The skill is not forced-always, and does not request elevated privileges or to modify other skills. Note: the agent can invoke the skill autonomously by default (platform normal), which would allow it to call Membrane commands if the runtime allows shell/CLI invocation—only enable autonomous use if you trust the environment.
Assessment
This skill appears internally consistent: it delegates auth and API calls to the Membrane platform and does not request unrelated secrets. Before installing or using it: 1) Verify the legitimacy of the @membranehq/cli npm package and publisher (review the package page, maintainers, and recent releases). 2) Prefer installing the CLI in a controlled environment (container or non-privileged account) if you don't want a global npm install. 3) Only allow autonomous agent invocation if you trust what the agent may run (it could execute CLI commands and make network requests). 4) If you need stronger assurance, ask the skill author for a signed/reproducible release URL or more documentation about the Amentum connector used by Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk97amf1z8kvjv4wwn9mdvgxsen84258j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.