Everestcard
v1.0.0Everestcard integration. Manage data, records, and automate workflows. Use when the user wants to interact with Everestcard data.
⭐ 0· 47·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
The SKILL.md explains using the Membrane CLI to connect to Everestcard, manage connections, run actions, and proxy API requests. The requested capabilities (network access and a Membrane account) match the described integration.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying requests. The document does not instruct reading unrelated system files, harvesting environment variables, or sending data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to install @membranehq/cli via npm (global install or npx). Installing a third-party npm CLI is expected for this workflow but does introduce typical supply-chain considerations (verify package identity and source).
Credentials
The skill declares no required environment variables or config paths. Authentication is delegated to Membrane and the SKILL.md explicitly advises not to collect API keys locally, which is proportionate to the described functionality.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It does not request special platform privileges or attempt to modify other skills or system-wide settings. Autonomous invocation is allowed by default, which is normal and not by itself concerning.
Assessment
This skill is coherent: it uses the Membrane CLI to talk to Everestcard and asks only for a Membrane account. Before installing or using it, verify the @membranehq/cli npm package and its publisher (to avoid malicious packages), confirm Membrane's privacy and data-handling practices (Membrane will proxy requests and therefore will have access to your Everestcard data once you create a connection), and review the permissions requested when you create the connector. Because the skill is instruction-only, the primary risk comes from installing/running the CLI and granting the connector access to your Everestcard account — not from hidden code inside the skill itself.Like a lobster shell, security has layers — review code before you run it.
latestvk971nmzsm0xdntdbjn99rszzzh84f4jr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.