Abyssale
v1.0.2Abyssale integration. Manage data, records, and automate workflows. Use when the user wants to interact with Abyssale data.
⭐ 0· 137·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
medium confidencePurpose & Capability
The skill claims to integrate with Abyssale and all runtime instructions use the Membrane CLI to discover connectors/actions and proxy API calls to Abyssale. The requested capabilities align with the stated purpose (discover actions, run them, or proxy requests).
Instruction Scope
SKILL.md keeps instructions focused on installing and using the Membrane CLI, creating connections, listing actions, and running actions or proxied requests. It does allow arbitrary proxied requests to Abyssale via Membrane (expected for an integration), but it does not instruct the agent to read unrelated local files or exfiltrate data. The file does not declare that the 'membrane' binary is required even though all runtime commands assume it is available.
Install Mechanism
There is no formal install spec in the registry metadata (instruction-only). The doc recommends installing @membranehq/cli from npm globally (npm install -g). This is a standard public npm package installation but the skill does not declare npm/node as a required binary. Installing a global npm package carries typical supply-chain/privilege considerations—users should verify the package and publisher before installation.
Credentials
The skill declares no required environment variables or secrets and explicitly advises against asking users for API keys, relying on Membrane to manage authentication. That is proportional to its stated function.
Persistence & Privilege
The skill does not request always:true, does not declare config paths, and is user-invocable only. It does not ask to modify other skills or system-wide settings.
Assessment
This skill is coherent and behaves as an Abyssale integration through Membrane, but before installing or running commands you should: 1) Confirm you trust the @membranehq/cli package and publisher (check the official repo and npm page), 2) ensure you are comfortable installing a global npm package (it requires npm/node and affects your system PATH), 3) prefer running installations in a controlled or sandboxed environment if you have security concerns, and 4) remember the Membrane proxy can forward arbitrary requests to Abyssale—only allow connections you trust. The only minor inconsistency is that the skill does not list 'npm'/'node' or the 'membrane' binary as required even though its instructions assume them; verify those prerequisites before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97cpeesn2r1n17wpbwm9hhwas8433vs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.