Microsoft Excel
v1.0.0Microsoft Excel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft Excel data.
⭐ 0· 63·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
Name/description indicate Microsoft Excel integration and the SKILL.md consistently instructs using Membrane to connect to Excel and run actions or proxied API requests. The requested capabilities (network access, Membrane account) align with that purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, authenticating via browser (or headless flow), listing/connecting actions, running actions, and optionally proxying API requests. The instructions do not ask the agent to read unrelated system files, exfiltrate arbitrary data, or access unexpected credentials.
Install Mechanism
No install spec is baked into the skill (instruction-only), but SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a reasonable delivery method for a CLI, but it pulls code from the public npm registry — vet the @membranehq/cli package and its version before installing and avoid running it on sensitive/shared hosts without review.
Credentials
The skill declares no required environment variables or secrets. It relies on interactive Membrane authentication (browser flow) to obtain Microsoft credentials, which is proportionate to the stated goal of controlling Excel via Membrane.
Persistence & Privilege
The skill is instruction-only, does not require always:true, and does not request persistent system-wide privileges. Autonomous invocation is allowed (platform default) but the skill itself does not attempt to modify other skills or system-wide settings.
Assessment
This skill appears coherent and is what it says: an instruction set for using the Membrane CLI to talk to Microsoft Excel. Before installing or running anything: (1) verify you trust the @membranehq/cli package (check its npm page, repository, and release/version), (2) review what OAuth scopes the Membrane connector will request when linking your Microsoft account, (3) run installs in a trusted environment (avoid shared or production machines until you vet the CLI), and (4) if you need tighter control, consider creating a service account or least-privilege account for integration rather than using a high-privilege personal account. If you want more assurance, supply the SKILL.md to a security reviewer or inspect the Membrane CLI source prior to installation.Like a lobster shell, security has layers — review code before you run it.
latestvk972hw5w375rpaccf6k8g31xjh84fyvq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.