Krayin
v1.0.0Krayin integration. Manage data, records, and automate workflows. Use when the user wants to interact with Krayin data.
⭐ 0· 33·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
medium confidencePurpose & Capability
The name/description (Krayin integration) match the SKILL.md: instructions show how to use the Membrane CLI to connect to Krayin, list actions, run actions, and proxy API requests. Required capabilities (network access, a Membrane account) are consistent with that purpose.
Instruction Scope
The runtime instructions are narrowly focused on installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to the Krayin API. Important: proxying and action execution sends requests through Membrane's servers and requires authenticating via the browser. The instructions do not ask the agent to read unrelated files, environment variables, or other system data.
Install Mechanism
There is no registry-level install spec, but the SKILL.md instructs users to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm package runs third‑party code on the host (moderate risk). This is expected for a CLI-based integration, but users should verify the package identity and trustworthiness before installing globally.
Credentials
The skill declares no required environment variables or credentials and explicitly advises not to collect local API keys. Authentication is delegated to Membrane and the browser login flow, which is proportional to the described integration.
Persistence & Privilege
The skill does not request persistent/always-on presence (always:false) and does not modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with broad privileges here.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Krayin. Before installing or using it, confirm the legitimacy of the @membranehq/cli package and the Membrane service (check official docs, GitHub repo, and package publisher). Consider installing or running the CLI in an isolated environment (container or VM) instead of globally if you want to limit risk. Remember that using the proxy or actions routes requests and data through Membrane's servers—do not send secrets or highly sensitive data unless you trust their service and privacy policy. If you need stricter control, prefer direct API credentials for Krayin (only if you control where those credentials are stored) or review Membrane's security documentation and access controls first.Like a lobster shell, security has layers — review code before you run it.
latestvk97737sr32ts3pjaa911faca05846963
License
MIT-0
Free to use, modify, and redistribute. No attribution required.