Microsoft Graph Api
v1.0.0Microsoft Graph API integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft Graph API data.
⭐ 0· 14·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 claims to provide Microsoft Graph integration and the SKILL.md exclusively documents using the Membrane CLI to connect to Graph, run pre-built actions, or proxy raw Graph requests. Required capabilities (network access, a Membrane account, the CLI) align with that purpose.
Instruction Scope
Runtime instructions are narrowly focused on installing and using @membranehq/cli, logging in, creating/using connections, listing actions, running actions, and proxying requests to Graph. The instructions do not direct the agent to read unrelated files, export arbitrary system state, or access unrelated environment variables.
Install Mechanism
The skill recommends installing a third-party npm CLI globally (npm install -g @membranehq/cli). This is a common and expected install method for a CLI but carries the usual npm-package risks (remote code execution via package install). The package is on the public npm registry and the SKILL.md references the project's repository/homepage, which makes the install traceable — review the package and its repository before installing.
Credentials
The skill declares no required environment variables or secrets. It relies on Membrane's authentication flow (browser-based login) rather than asking for API keys, which is proportionate. Note: the Membrane CLI and/or Membrane service will manage and persist auth tokens for connections (server-side or in local CLI config), so you should trust the vendor or inspect where tokens are stored if that matters.
Persistence & Privilege
The skill is not marked always:true and is user-invocable only. There is no instruction to modify other skills or global agent configs. Installing the CLI will write files/binaries to disk and the CLI will store connection credentials/config locally or server-side, which is normal for a CLI integration.
Assessment
This skill is coherent with its stated purpose, but it depends on a third‑party CLI. Before installing: (1) verify the @membranehq/cli package and its GitHub repo (authorship, recent activity, and issues); (2) understand that the CLI will open a browser to authenticate and will persist tokens/config locally or manage them via Membrane's service — if you have strict data policies, check where those tokens are stored and how Membrane handles data; (3) prefer installing in a controlled environment (container/VM) if you want to limit blast radius; and (4) do not paste unrelated secrets into CLI commands. If you need higher assurance, ask the skill author for more details about how credentials are stored and for a reproducible provenance link to the npm package and project source.Like a lobster shell, security has layers — review code before you run it.
latestvk975pnnfz5ydn4wxz22sp30rrd848phj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.