Frontegg

v1.0.2

Frontegg integration. Manage data, records, and automate workflows. Use when the user wants to interact with Frontegg data.

0· 124·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name/description (Frontegg integration) matches the instructions: it instructs the agent to use the Membrane CLI to connect to and operate on Frontegg. Asking the user to install @membranehq/cli and to authenticate via a browser is coherent with the stated purpose.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI to list connections, run actions, and proxy API requests. They do not ask the agent to read unrelated files or environment variables. Note: the workflow routes Frontegg API calls through Membrane's proxy, meaning Membrane will see/handle authentication and proxied requests — this is expected but worth the user's attention.
Install Mechanism
There is no embedded install spec; the SKILL.md instructs the user to run `npm install -g @membranehq/cli`. Installing an npm package globally is a normal way to get the CLI but carries the usual risks of running third-party npm code; the source (membranehq on npm, repository linked to membranedev) appears consistent with the documentation.
Credentials
The skill does not request environment variables, local config paths, or unrelated credentials. Authentication is performed via Membrane (browser login/connection flow), which is proportionate to a third-party integration skill.
Persistence & Privilege
The skill does not request always-on presence and has defaults for autonomous invocation. It does not instruct modifying other skills or system-wide agent settings. No elevated persistence or privilege is requested.
Assessment
This skill is coherent but depends on the Membrane service and its CLI. Before installing or using it: 1) Verify you trust Membrane (https://getmembrane.com and the linked GitHub repo) because Membrane will see proxied Frontegg requests and manage credentials; 2) Be aware `npm install -g @membranehq/cli` executes third-party code—install in a controlled environment or review the package if you have concerns; 3) The login flow opens a browser for auth and issues a connection ID that grants access to Frontegg data—treat that connection like a credential; 4) Do not provide unrelated local secrets to this skill, and audit Membrane's privacy/security docs if you must handle sensitive data.

Like a lobster shell, security has layers — review code before you run it.

latestvk974ret4zb9bd301d5he3f3181842q6s

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments