Azure Api Management
v1.0.2Azure API Management integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure API Management data.
⭐ 0· 97·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 claims to integrate with Azure API Management and all runtime instructions use the Membrane CLI to perform that work — this aligns with the stated purpose. Minor inconsistency: the SKILL.md requires installing the Membrane CLI via `npm install -g`, but the registry metadata declares no required binaries; node/npm should be declared.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, creating a connection, listing actions, running actions, and proxying requests to the Azure API Management API. The instructions do not ask the agent to read unrelated files or environment variables. They do rely on browser-based auth (or a headless flow) and on Membrane to manage credentials.
Install Mechanism
There is no embedded install spec, but the skill instructs the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a typical, moderate-risk install mechanism (npm packages can include install scripts). The SKILL.md does not provide alternate install options or declare the need for node/npm.
Credentials
The skill requests no environment variables or credentials itself and explicitly delegates credential management to Membrane. Requiring a Membrane account and network access is proportionate to the stated functionality. There are no unrelated credential requests.
Persistence & Privilege
The skill does not request persistent platform privileges and is not always-enabled. The main persistence concern is that the Membrane CLI will manage authentication tokens (likely stored locally or server-side via Membrane) — this is expected for a CLI-driven integration and is within scope.
Assessment
What to consider before installing:
- The skill expects you to install and run the Membrane CLI from npm; ensure you have node/npm and that the registry package `@membranehq/cli` and the project (https://github.com/membranedev/application-skills and https://getmembrane.com) are from a trusted source before running a global install.
- Global npm installs run package install scripts and can execute code on your machine — prefer reviewing the package and its repository, or install in a controlled environment (container/VM) if you are unsure.
- Membrane will handle Azure credentials; verify where the CLI stores tokens (local config) and understand that connecting to Azure via Membrane gives the Membrane service the ability to act on your APIs — only connect accounts you trust to that provider.
- If you require stricter controls, consider using an isolated environment for the CLI or reviewing Membrane's privacy/security docs and source code before connecting sensitive Azure subscriptions.
- Minor metadata gap: the skill should declare node/npm as a required binary; if you install, be prepared to satisfy that dependency.Like a lobster shell, security has layers — review code before you run it.
latestvk971gys6dgtebhntw88sye8md5842zwy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
