Apideck
v1.0.0Apideck integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apideck data.
⭐ 0· 28·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 is named 'Apideck' and describes Apideck integration but explicitly instructs the agent to use the Membrane CLI to access Apideck. This is a minor naming/branding mismatch but functionally coherent: Membrane is presented as the proxy to Apideck and the required CLI is appropriate for that purpose.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, performing login (browser-based or headless flow), listing/connecting actions, running actions, and proxying requests to Apideck via Membrane. It does not instruct the agent to read unrelated system files, environment variables, or exfiltrate data to unexpected endpoints.
Install Mechanism
No registry install spec exists (instruction-only), but the README directs users to install @membranehq/cli via npm (npm install -g). Installing a public npm CLI is typical for this use-case; supply-chain risk exists for any npm package, but the instruction is proportional and uses a normal package registry rather than arbitrary downloads.
Credentials
The skill declares no required env vars or credentials. It relies on Membrane's interactive login flow for auth, which is appropriate for a connector integration and avoids requesting unrelated secrets.
Persistence & Privilege
The skill does not request always:true or any elevated platform privileges. The Membrane CLI will create local auth/session state as part of normal login flows, which is expected behavior for a CLI used to access external services.
Assessment
This skill appears to do what it says: it instructs use of the Membrane CLI to access Apideck and asks for no extra credentials. Before installing, verify the @membranehq/cli package on npm (publisher and download counts), consider using npx instead of a global npm install in shared environments, and confirm the repository/homepage (getmembrane.com) matches your expectations. Be aware the CLI login will open a browser or produce a URL and will store local session data/tokens as part of normal operation — don't paste any unrelated secrets into the chat. If you need higher assurance, review the @membranehq/cli source code (the provided repo link) before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk970c8an9q79fcw85yd2t5j4sx8460tn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.