Azure Ai Vision
v1.0.2Azure AI Vision integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure AI Vision data.
⭐ 0· 104·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 (Azure AI Vision integration) matches the instructions: all runtime steps use the Membrane CLI to discover connectors, run actions, or proxy requests to Azure AI Vision. There are no unrelated requirements (no AWS keys, no unrelated binaries).
Instruction Scope
Instructions are narrowly focused on installing and using the Membrane CLI, creating a Membrane connection to Azure AI Vision, listing actions, running actions, and proxying raw requests. However, the skill routes requests through Membrane's service (it explicitly says Membrane will inject authentication and proxy requests). That means user images/data and requests will flow via Membrane rather than a direct Azure SDK call — a privacy/third-party data-flow consideration the user should be aware of.
Install Mechanism
There is no declared install spec in the registry (instruction-only), but the SKILL.md instructs the user to run `npm install -g @membranehq/cli`. Installing a third-party global npm package is a real action with moderate risk (pulls code from the npm registry). This is expected for using the Membrane CLI but worth noting because it executes code under your account/machine when installed.
Credentials
The skill declares no required environment variables or credentials. The SKILL.md directs users to authenticate via Membrane (browser flow) and explicitly advises not to ask users for API keys — this aligns with the stated design and is proportional.
Persistence & Privilege
The skill is not always-enabled and does not request special platform privileges. It's instruction-only and does not write persistent configuration or modify other skills. Autonomous model invocation is allowed by default but not combined with other concerning signals.
Assessment
This skill is coherent, but before installing or using it you should: (1) accept that requests and data (images/text) will be proxied via Membrane — review Membrane's privacy and terms if you will send sensitive content; (2) verify the @membranehq/cli package and the Membrane account are trustworthy before running a global npm install; (3) prefer testing with non-sensitive data first; and (4) if you require direct, auditable Azure-only access (no third-party proxy), consider connecting directly to Azure instead of using a proxy service.Like a lobster shell, security has layers — review code before you run it.
latestvk977x65we4z7k5t93vjj7jygc1842x4y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.