Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Ready2Order

v1.0.0

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

0· 41·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
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The SKILL.md describes exactly how to interact with Ready2order via the Membrane CLI (discover actions, run actions, proxy raw API requests). That matches the skill name/description. However, the registry metadata declared no required binaries or credentials while the instructions require installing and using the Membrane CLI (npm) and a Membrane account — a mismatch between declared requirements and the runtime steps.
Instruction Scope
The runtime instructions are narrowly scoped to using the Membrane CLI to create connections, list actions, run actions, and proxy requests to the Ready2order API. The instructions do not ask the agent to read arbitrary local files or other unrelated environment variables. Note: the proxy capability allows arbitrary HTTP requests to the API via Membrane, which is expected for this integration but increases what authenticated sessions can do.
Install Mechanism
There is no formal install spec in the registry, but the SKILL.md instructs the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a common but non-trivial step (requires npm/node and network access). This is a traceable npm package (not an unknown URL), but the registry's omission of a required-binaries/install declaration is an inconsistency worth noting.
Credentials
The skill declares no required environment variables or config paths and explicitly recommends not asking the user for API keys (Membrane handles auth). In practice the Membrane CLI performs an interactive login (browser flow) and will persist credentials/config locally (not documented in the registry). The skill does not declare where those tokens/config are stored — this is a gap between declared and actual credential handling.
Persistence & Privilege
The skill is not forced-always and is user-invocable (normal). The skill itself does not request elevated platform privileges. Installing the Membrane CLI creates a persistent binary on the system, but that is a user-side installation step rather than an automatic change made by the skill. Be mindful that once authenticated, actions run through Membrane can act on the user's Ready2order data.
What to consider before installing
This skill appears to do what it says (integrate with Ready2order via Membrane), but there are a few practical gaps to consider before proceeding: - The SKILL.md instructs you to install @membranehq/cli with npm (global install). That requires node/npm and will add a persistent binary; the registry metadata did not declare this dependency. Only install if you trust the upstream package and its publisher. - The Membrane login is an interactive browser auth flow and will store tokens/config locally. The skill does not document where credentials are persisted. Review Membrane's docs and local config paths before authenticating. - The Membrane proxy lets you send arbitrary HTTP requests to Ready2order on behalf of your authenticated connection. Treat the connection like a live API credential: only grant access if you trust the CLI/service and the agent invocation context. - Verify the @membranehq/cli package and the repository (https://github.com/membranedev/application-skills and the Membrane project) on npm/GitHub for legitimacy and recent activity. Prefer using the CLI in an environment you control and avoid installing global packages on sensitive machines if you are unsure. If you want a cleaner security posture, ask the skill author/registry to: declare required binaries (node/npm, membrane), add an install spec or explicit notes about config/credential storage paths, and explain where local tokens are stored and how to revoke connections.

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

latestvk977gnqh2z7ahcpe7q55r0m9qs84fxyw

License

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

Comments