Loginid
v1.0.2LoginID integration. Manage data, records, and automate workflows. Use when the user wants to interact with LoginID data.
⭐ 0· 119·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 claims to integrate with LoginID and its SKILL.md consistently instructs use of the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests to LoginID. The homepage and repository references point to Membrane resources, which aligns with the stated purpose.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying requests. This stays within the integration's scope. Note: running 'membrane request' allows arbitrary proxied requests to LoginID endpoints (expected for a proxy-based integration) — users should be aware that granting a connection delegates API access to Membrane.
Install Mechanism
No registry install spec is provided, but SKILL.md instructs installing @membranehq/cli via 'npm install -g'. This is a standard public npm install instruction and proportional to the CLI-driven workflow, but it does require installing third-party software globally and network access; users should verify the package and prefer scoped or ephemeral installs if concerned.
Credentials
The skill declares no required environment variables or credentials; authentication is delegated to Membrane's login flow. That is proportionate to the purpose. Users should nonetheless recognize that authentication grants Membrane server-side access to the connected LoginID account.
Persistence & Privilege
The skill does not request always-on presence and is user-invocable. There is no install-time modification of other skills or system-wide settings described. Autonomous invocation is allowed (platform default) but is not combined with other concerning privileges.
Assessment
This skill is internally consistent: it requires installing the Membrane CLI and creating a Membrane connection to LoginID, which is how it achieves its stated purpose. Before installing or using it, verify you trust Membrane (@membranehq), review their privacy/security docs and OAuth scopes, and consider using a test/limited LoginID account. Installing the CLI globally requires npm and network access — if you prefer less risk, run the CLI in a constrained environment (container or ephemeral VM) or use npx instead of a global install. Be aware that the Membrane connection will proxy API calls and effectively grant Membrane server-side access to the LoginID resources you connect.Like a lobster shell, security has layers — review code before you run it.
latestvk975jfcd0e1x8hb8gpw3qpbr2d842zv5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.