Clerkio
v1.0.0Clerk.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clerk.io data.
⭐ 0· 91·0 current·0 all-time
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 described as a Clerk.io integration and all runtime instructions use the Membrane CLI to connect to Clerk.io and run actions, which is consistent. Minor inconsistency: registry metadata lists no required binaries, but the SKILL.md tells users to install the @membranehq/cli (npm) — this is expected for functionality but the registry metadata should have declared that requirement.
Instruction Scope
SKILL.md limits runtime actions to using the Membrane CLI (login, connect, action list/run, and proxy to Clerk.io). It does not instruct reading unrelated local files, environment variables, or exfiltrating data. It explicitly advises against asking users for API keys and recommends letting Membrane handle credentials.
Install Mechanism
There is no formal install spec in the registry; the instructions tell users to run `npm install -g @membranehq/cli`. Installing a public npm CLI globally is a common pattern but carries moderate risk (global package install, trust in the package). No downloads from untrusted URLs or archive extraction are used.
Credentials
The skill does not request environment variables or local credentials. It relies on a Membrane account and browser-based authentication; this is proportionate to a third-party integration and reduces direct exposure of Clerk.io API keys to the agent.
Persistence & Privilege
Flags show normal defaults (not always: true). The skill is instruction-only and does not request persistent system-wide privileges or change other skills' configurations.
Assessment
This skill delegates auth and API calls to Membrane and asks you to install the @membranehq/cli (npm). Before installing or using it: 1) Confirm you trust Membrane and the @membranehq/cli package (review their homepage, repository, and npm page). 2) Be aware you will authenticate via your browser and grant Membrane access to your Clerk.io account—check Membrane's privacy and access policies. 3) Prefer installing the CLI in a controlled environment (avoid unexpected global npm installs on critical systems). 4) If you need higher assurance, inspect the Membrane CLI source and the referenced repository, and verify network requests or use an isolated/test account for initial runs.Like a lobster shell, security has layers — review code before you run it.
latestvk97ave57yt1gwr5mga2swj0khs84hdds
License
MIT-0
Free to use, modify, and redistribute. No attribution required.