Clerkio
v1.0.0Clerk.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clerk.io data.
⭐ 0· 93·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
high confidencePurpose & Capability
The skill is an integration that operates through the Membrane CLI to access Clerk.io resources. Requiring a Membrane account and the Membrane CLI is consistent with the described functionality; no unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating a connection to Clerk.io, listing/running actions, and proxying API requests. It does not instruct reading unrelated files, accessing extraneous environment variables, or transmitting data to unexpected endpoints. Network access and a Membrane account are explicitly required.
Install Mechanism
The registry has no install spec (lowest registry risk), but the README instructs installing @membranehq/cli via 'npm install -g'. Installing a global npm package from the public registry is a normal approach but carries the usual trust considerations for third-party npm packages.
Credentials
No environment variables or secrets are requested by the skill. SKILL.md explicitly advises letting Membrane manage credentials rather than asking users for API keys, which is proportionate to the integration's design.
Persistence & Privilege
The skill is not marked 'always: true' and does not request persistent system-wide privileges or modify other skills' configs. Autonomous invocation is allowed (platform default) and is not combined with other red flags.
Assessment
This skill delegates Clerk.io access to the Membrane service and its CLI. Before installing or using it: (1) Confirm you trust Membrane (getmembrane.com) because authentication and API requests will be proxied through their service; review their privacy, security, and data-retention policies. (2) Be aware that installing '@membranehq/cli' globally gives that CLI access on the host — only install packages you trust and consider using a scoped/local install if appropriate. (3) Understand that once you create a connection, Membrane will be able to act on Clerk.io data for that account/connection; use least-privilege credentials or a dedicated account if you want to limit risk. (4) Verify connector IDs and action IDs come from the Membrane account UI/official CLI outputs (avoid pasting tokens/IDs from untrusted sources). (5) If you need higher assurance, review Membrane's audit logs, network endpoints, and the referenced repository/homepage before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97dhqv0q7nbb2v3pkrvra9wrs84gtbp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.