Tito
v1.0.0Tito integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tito data.
⭐ 0· 56·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 declares it integrates with Tito and all runtime instructions use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to the Tito API. It does not request unrelated credentials, binaries, or system access.
Instruction Scope
SKILL.md stays within the integration scope: install the Membrane CLI, authenticate, create/lookup a Tito connection, run actions, or proxy raw API requests. It does not instruct reading unrelated files, exposing local secrets, or transmitting data to destinations outside Membrane/Tito.
Install Mechanism
There is no automated install spec in the registry, but the instructions tell users to run `npm install -g @membranehq/cli`. Installing a CLI from npm is a normal, moderate-risk action — verify the package and source before global install. No downloads from arbitrary URLs or archive extraction are present in the skill itself.
Credentials
The skill requests no environment variables or local credentials; it explicitly relies on Membrane to manage auth and credential refresh server-side. Requiring a Membrane account and network access is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request persistent/always-on inclusion (always: false) and contains no instructions to modify other skills or global agent configuration. Autonomous invocation is allowed (default) but is not combined with other concerning privileges.
Assessment
This skill is coherent and appears to do what it says: it uses the Membrane CLI to talk to Tito. Before installing or running the CLI, verify the @membranehq/cli npm package and the vendor (getmembrane.com). If you manage sensitive environments, prefer installing the CLI in an isolated environment or container rather than globally. When authenticating, review the connector permissions shown by Membrane so you know what access is being granted to Tito data. If your organization restricts third-party CLIs, consult your security team first.Like a lobster shell, security has layers — review code before you run it.
latestvk976aqpkbq0ad3atyg0r3e5dhx84ca3h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.