Regal
v1.0.2Regal integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Regal data.
⭐ 0· 116·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 name/description (Regal integration) matches the instructions: all runtime actions are mediated via the Membrane CLI and Membrane connections to Regal. There are no unrelated credentials, binaries, or capabilities requested.
Instruction Scope
SKILL.md confines actions to installing and using the Membrane CLI (login, connect, action list/run, proxy requests). It does not instruct reading unrelated files, environment variables, or sending data to unexpected endpoints — proxy requests go to Regal via the Membrane service as described.
Install Mechanism
There is no formal install spec in the registry (skill is instruction-only). The instructions ask the user to install the @membranehq/cli via npm -g or use npx. Installing a global npm package is a normal step for a CLI-based integration but does execute third-party code on the host; users should verify the package and source before installing.
Credentials
The skill requests no environment variables or credentials and explicitly says to let Membrane handle auth. That is proportionate for a connector that relies on a third-party CLI/service for credentials.
Persistence & Privilege
The skill does not request 'always' presence or system-level changes. It is user-invocable and does not attempt to modify other skills or persistent agent configs in the instructions.
Assessment
This skill is instruction-only and appears coherent: it tells you to use the Membrane CLI to connect to Regal rather than asking for direct API keys. Before installing the CLI, verify the @membranehq/cli package and its repository (npm and GitHub links) to ensure you trust the publisher. Installing a global npm package runs third-party code on your machine — consider using npx or a container if you prefer not to install globally. When using membrane request (proxy) be careful to run requests only against known connection IDs and paths for the intended account so you don't accidentally expose or act on unrelated resources.Like a lobster shell, security has layers — review code before you run it.
latestvk976y6fc1cyv071rm56rnrh8fd842dgq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.