Cloud Foundry
v1.0.0Cloud Foundry integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloud Foundry data.
⭐ 0· 13·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/description (Cloud Foundry integration) align with the instructions: it tells the user to use the Membrane CLI and Membrane connections to interact with Cloud Foundry APIs. Nothing requested (no env vars, no config paths) is unrelated to that purpose.
Instruction Scope
The SKILL.md instructs installing and using the @membranehq/cli, creating connections, listing and running actions, and proxying requests to Cloud Foundry via Membrane. It does not tell the agent to read local credentials or unrelated system files. Note: the proxy feature can send arbitrary requests to Cloud Foundry APIs via Membrane, which is expected for this integration but means the Membrane account/connection will have broad access to CF resources.
Install Mechanism
There is no automated install spec in the registry (instruction-only). The docs recommend installing the Membrane CLI via npm (npm install -g @membranehq/cli). This is a normal, low-risk instruction; the skill itself does not download arbitrary code or include extractable archives.
Credentials
The skill declares no required environment variables or credentials. SKILL.md explicitly says Membrane handles credentials server-side and advises not to ask users for API keys. The level of access requested (a Membrane account + connection to Cloud Foundry) is proportional to the stated purpose.
Persistence & Privilege
The skill is not always-enabled and does not request persistent platform privileges. It is user-invocable and allows autonomous model invocation by default (the platform default), which is appropriate for an integration skill.
Assessment
This skill is instruction-only and appears coherent: it relies on the Membrane platform (getmembrane.com) to authenticate and proxy requests to Cloud Foundry. Before installing or following its instructions, confirm you trust the Membrane service because it will hold and use credentials for Cloud Foundry connections and can perform arbitrary CF API calls on your behalf. If your organization restricts global npm installs, or requires review of third-party services, review @membranehq/cli source and Membrane's security/privacy docs and the referenced GitHub repository first. Otherwise the skill's requests and instructions are proportional to its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk9763d2c3taj1t0kgc81r7z27n84d6jk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.