Typesense
v1.0.2Typesense integration. Manage data, records, and automate workflows. Use when the user wants to interact with Typesense data.
⭐ 0· 150·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 name/description (Typesense integration) matches the instructions: everything is done via the Membrane CLI which provides Typesense connectors and proxying. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md confines runtime behavior to installing/using the Membrane CLI, creating/listing connections, running actions, and proxying requests to Typesense. It does not instruct reading arbitrary files, environment variables, or sending data to unexpected endpoints beyond Membrane/Typesense.
Install Mechanism
There is no automatic install spec; the doc instructs users to run `npm install -g @membranehq/cli`. Global npm installs are a common way to install CLIs but carry the usual supply-chain/trust considerations for npm packages (moderate risk).
Credentials
The skill requests no environment variables or local secrets and explicitly advises relying on Membrane for credential handling. The only required external account is a Membrane account, which is proportionate to the documented workflow.
Persistence & Privilege
The skill is not set always:true and does not request persistent or elevated agent privileges. It is instruction-only and relies on user-driven CLI actions, not on modifying other skills or system-wide settings.
Assessment
This skill appears coherent, but before installing: 1) Verify you trust Membrane (@membranehq) and review their privacy/security docs since requests and credentials will be proxied through their service. 2) Inspect the npm package and its repository (source code, recent commits, maintainers) before running a global install. 3) If your Typesense data is sensitive, confirm what data will traverse Membrane and whether you accept that third-party routing. 4) Use least-privilege connections when creating the connector (avoid giving full admin credentials unless required). 5) In headless or automated environments, ensure the login flow and stored credentials meet your security policies.Like a lobster shell, security has layers — review code before you run it.
latestvk97170wtt5qckwd14q554sxya5843yhf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.