Kilo Ssl
v1.0.0Kilo SSL integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kilo SSL data.
⭐ 0· 53·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 and description match the runtime instructions: the skill consistently describes interacting with Kilo SSL via the Membrane CLI and does not ask for unrelated cloud credentials or system-level access.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in, creating or listing connections, running actions, and proxying requests through Membrane. It does not direct reading arbitrary files, harvesting environment variables, or sending data to unexpected endpoints beyond the Membrane/Kilo SSL flow.
Install Mechanism
There is no registry install spec, but the instructions recommend installing @membranehq/cli via npm (-g). This is a standard public npm package installation (moderate risk compared to instruction-only). Verify the package publisher and intended version before global installation, since npm packages run install-time scripts and will write to disk.
Credentials
The skill declares no required env vars or credentials and explicitly instructs not to collect local API keys. Authentication is delegated to Membrane via browser login and connector flows, which is proportionate to the described integration.
Persistence & Privilege
always is false and the skill is instruction-only with no install-time modifications recorded. It does not request persistent system-wide privileges or modifications to other skills' configs.
Assessment
This skill appears coherent: it uses the Membrane CLI to access Kilo SSL and asks you to authenticate via the Membrane account. Before installing or running commands: 1) verify the @membranehq/cli package on npm (publisher, version, and popularity) to ensure you trust the source; 2) use an account with least-privilege and review the connector's scope/permissions in Membrane (the connector will be able to act on Kilo SSL data); 3) be aware that the `membrane request` proxy can send arbitrary requests through the connection—avoid passing sensitive local files or secrets through it; 4) prefer using npx for one-off commands to avoid global installs if you want to limit system changes. If you need deeper assurance, request the skill author or publisher details and an audit of the @membranehq/cli package.Like a lobster shell, security has layers — review code before you run it.
latestvk97a96426rc9myc8a7n5htd33x848rcw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.