Typless
v1.0.2Typless integration. Manage data, records, and automate workflows. Use when the user wants to interact with Typless data.
⭐ 0· 66·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 and description match the instructions: the SKILL.md consistently describes interacting with Typless via the Membrane platform/CLI. Requests and actions (discover actions, run actions, proxy requests) are coherent with a Typless integration.
Instruction Scope
Instructions stay within the integration scope (install CLI, login, create connections, run actions, proxy API calls). One note: the proxy feature lets the agent send arbitrary HTTP requests to Typless through Membrane (expected for this use case) — be aware this can transmit user data to Membrane/Typless as part of normal operation.
Install Mechanism
The skill is instruction-only (no automatic installer), but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal step for using a CLI but carries the usual risk of executing third-party code from the registry; this is expected for a CLI-driven integration.
Credentials
The skill requests no environment variables or local credentials and explicitly instructs not to ask the user for API keys, relying on Membrane-managed connections — this is proportionate to the stated purpose.
Persistence & Privilege
No special persistence flags are set (always:false). The skill does not request system-wide config access or modify other skills. Autonomous invocation is allowed by platform default and not a specific concern here.
Assessment
This skill is coherent and uses the Membrane CLI to access Typless. Before installing/using it: (1) confirm you trust the @membranehq npm package and review its README/source if possible; (2) understand that Membrane will broker authentication and may receive proxied requests and data — review Membrane's privacy/security docs and the permissions shown during connector OAuth flows; (3) avoid pasting secrets into chat—follow the connection flow so credentials stay managed by Membrane; (4) in headless or shared environments, ensure the login codes/URLs are handled securely. If you want higher assurance, ask for the skill's source (repo link or package checksum) to verify the CLI package and instructions.Like a lobster shell, security has layers — review code before you run it.
latestvk97annmhn7dze4zdtzjhp1dqf184243y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.