Pulumi

v1.0.0

Pulumi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pulumi data.

0· 56·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill claims Pulumi integration and the SKILL.md consistently describes using the Membrane CLI/proxy to access Pulumi APIs and actions. The declared requirements (network and a Membrane account) match this purpose; no unrelated services or credentials are requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in, creating/listing connections, running actions, and optionally proxying raw requests to the Pulumi API. There are no instructions to read unrelated local files, export environment secrets, or transmit data to unexpected endpoints beyond the Membrane/Pulumi flow.
Install Mechanism
The skill is instruction-only (no automatic install). It recommends installing @membranehq/cli via npm -g or using npx. This is a normal, moderate-risk instruction (global npm installs modify the system PATH); users should verify the package source before installing.
Credentials
The skill declares no required environment variables or local secrets. Authentication is handled by Membrane (server-side), which is consistent with the stated guidance to avoid local API keys. Users must trust Membrane to hold and refresh Pulumi credentials.
Persistence & Privilege
The skill does not request persistent or elevated privileges (always: false). It is instruction-only and does not install background services or modify other skills' configurations.
Assessment
This skill is coherent: it uses the Membrane CLI to proxy Pulumi actions and does not ask for unrelated credentials. Before installing or using it: (1) verify the @membranehq/cli package and the Membrane service (homepage/repo) are legitimate and trustworthy, (2) prefer using npx or a local install if you want to avoid a global npm -g install, (3) understand that Pulumi credentials will be managed server-side by Membrane—only proceed if you trust that service, and (4) review any connections you create to ensure they grant least privilege to your Pulumi organization/projects.

Like a lobster shell, security has layers — review code before you run it.

latestvk971ad6hg8c9ymsx769xmzbcax84ej5m

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments