Singular
v1.0.2Singular integration. Manage data, records, and automate workflows. Use when the user wants to interact with Singular data.
⭐ 0· 68·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's name/description (Singular integration) matches the runtime instructions: all actions are performed through the Membrane CLI and/or Membrane's proxy to Singular. There are no unrelated required env vars, binaries, or config paths requested by the skill.
Instruction Scope
SKILL.md confines actions to installing/running the Membrane CLI, creating connections, listing/running actions, and proxying requests to Singular. It does not instruct reading arbitrary local files or harvesting unrelated credentials. Note: proxying requests via Membrane means user data and API calls will flow through Membrane's service, which is expected for this integration.
Install Mechanism
The registry provides no automated install spec (this is instruction-only). The SKILL.md recommends running `npm install -g @membranehq/cli` (a normal step), but that is a manual global npm install — installing packages globally executes third-party code on the machine. Consider using npx or verifying the package/source before installing.
Credentials
No environment variables, credentials, or config paths are required by the skill. The instructions explicitly say to let Membrane handle credentials and not to ask users for API keys, which is proportionate for a connector-based integration.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It is instruction-only and does not modify other skills or global agent settings.
Assessment
This skill is coherent, but before installing or using it: 1) Verify the authenticity of the @membranehq/cli package (check the npm page, repository, and publisher) or use `npx @membranehq/cli` to avoid a global install. 2) Understand that Membrane will proxy API calls and manage credentials server-side — any data you send to Singular via this flow will pass through Membrane's service, so review their privacy/security policies. 3) Use the browser-based login flow as instructed (copying URLs/codes only from the CLI output), and avoid entering sensitive secrets into untrusted pages. 4) Prefer least-privilege connections and review the connector’s permissions after creating it. If you need an automated install or want the skill to run without manual CLI installation, request the publisher add a formal install spec or clarify provenance.Like a lobster shell, security has layers — review code before you run it.
latestvk974383cqhvk425rx6kxfjq0y5843vbh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.