Sheety

v1.0.0

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

0· 60·0 current·0 all-time
byMembrane Dev@membranedev
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 name/description (Sheety integration) matches the runtime instructions, which exclusively describe using the Membrane CLI to discover and run Sheety actions or proxy raw Sheety API calls. No unrelated credentials, binaries, or filesystem access are requested.
Instruction Scope
Instructions stay within the Sheety use-case (membrane login, connect, action list/run, request proxy). They do, however, rely on Membrane's proxy and authentication flow, which means Sheety requests, responses and auth flows will be routed through Membrane's service — a privacy/trust consideration rather than unexpected functionality.
Install Mechanism
No install spec in the registry, but SKILL.md instructs users to run `npm install -g @membranehq/cli`. Installing a CLI from the public npm registry is a typical choice but carries the normal supply-chain risk of executing third-party code; this is expected for a CLI-based integration.
Credentials
The skill declares no required env vars or local config paths and explicitly advises not to ask users for API keys. Authentication is delegated to Membrane; the palette of requested access is minimal and proportional to the stated purpose.
Persistence & Privilege
The skill does not request always-on inclusion, does not modify other skills, and contains no installation scripts in the registry. It is instruction-only and will only act when invoked.
Assessment
This skill is coherent: it uses the Membrane CLI to reach Sheety rather than asking for your Sheety/Google credentials directly. Before installing or using it, verify that you trust Membrane because requests, responses, and authentication flows will be routed through Membrane's service and the global npm package will execute third-party code on your machine. Consider using npx (e.g., `npx @membranehq/cli ...`) for a one-off invocation or review the @membranehq/cli package source and permissions on npm/GitHub. Also review Membrane's privacy/security docs and ensure you are comfortable granting it access to the Google Sheet data you plan to manage.

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

latestvk97df7yzbtsfs3tkhzmk09j87n84a4ys

License

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

Comments