Winston Ai
v1.0.0Winston AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with Winston AI data.
⭐ 0· 47·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the SKILL.md explains how to use the Membrane CLI to interact with Winston AI. No unrelated credentials, binaries, or capabilities are requested.
Instruction Scope
The instructions are limited to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. They do not ask the agent to read arbitrary files, harvest environment variables, or send data to unexpected endpoints.
Install Mechanism
No install spec embedded in the skill (instruction-only). The README instructs users to run `npm install -g @membranehq/cli` or use npx; this is an expected, moderate-risk npm install for the described purpose. Review the CLI package/repo before installing global npm binaries.
Credentials
The skill declares no required env vars and instructs the user to use Membrane-managed authentication (browser login). Note: Membrane will proxy requests and handle credentials server-side, so data and auth tokens will transit/work via Membrane's service—confirm you trust getmembrane.com and the Membrane service's privacy/security posture.
Persistence & Privilege
No special persistence or 'always' privilege is requested. The skill is user-invocable and can be used autonomously by the agent (platform default), which is expected for a connector-style skill.
Assessment
This skill is instruction-only and coherent: it tells the agent to use the Membrane CLI to connect to Winston AI and run actions. Before installing or following the instructions: (1) verify you trust Membrane/getmembrane.com and review the @membranehq/cli package/repo, (2) understand that Membrane will proxy requests and handle credentials server-side (your data will flow through their service), (3) be cautious installing global npm packages—prefer using npx or reviewing the package first, and (4) in headless or automated environments, confirm how the browser-based login flow will be completed so credentials are not exposed. If you need stronger guarantees, review Membrane's privacy/security docs or use a vetted alternative.Like a lobster shell, security has layers — review code before you run it.
latestvk975rpkv2jwc9z7wve0ddjcx4d84fwmk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.