Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Polymer
v1.0.0Polymer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Polymer data.
⭐ 0· 19·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
Suspicious
medium confidencePurpose & Capability
The skill is named and described as a 'Polymer' integration for managing data and workflows, and the runtime instructions focus on using the Membrane CLI to proxy requests to a Polymer API — that is plausible. However the SKILL.md also contains an unrelated high-level description and links for the Polymer JavaScript UI library (front-end framework), which does not match the integration usage later in the file. The registry metadata declares no required binaries or credentials, but the instructions explicitly require installing and running @membranehq/cli and an active Membrane account. This mismatch between declared requirements and actual instructions is incoherent.
Instruction Scope
Runtime instructions tell the agent/operator to install the Membrane CLI, run interactive login (including headless flow), create a connector, list and run actions, and use 'membrane request' to proxy arbitrary Polymer API endpoints. Proxying arbitrary endpoints means requests and payloads will traverse Membrane's servers and Membrane will hold authentication for the target service — expected for this integration but it does give an external service (Membrane) access to whatever data you send. The instructions do not tell the agent to read local files or extra environment variables, so there is no direct local exfiltration instruction, but the documentation is somewhat vague about what data might be proxied and logged by Membrane.
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md instructs installing the Membrane CLI with 'npm install -g @membranehq/cli'. That is a manual, elevated (global) npm install performed outside the package registry. npm installs are common but carry moderate risk — the registry should have declared the required binary or provided an install spec. The absence of an explicit install block plus a global npm install instruction is an inconsistency and means users must verify the CLI package on npm before installing (or install it in an isolated environment).
Credentials
The skill declares no required environment variables or credentials, and the SKILL.md states Membrane manages credentials server-side and recommends not asking the user for API keys. That is proportionate. Note: using Membrane means that Membrane will hold the auth for target Polymer services and will see any requests made via the proxy, so the trust boundary shifts to Membrane rather than to local env vars.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system-level privileges. It is instruction-only with no code files, so it does not install components on the agent by itself. The skill uses the platform default allowing autonomous invocation; combined with the remote-proxy behavior, an autonomously-invoked agent could perform API calls via a previously-created Membrane connection — this is expected but worth noting as an operational consideration.
What to consider before installing
Things to consider before installing/using this skill:
- Clarify intent: ask the publisher what 'Polymer' refers to here (the frontend Polymer JS library versus a Polymer data API). The SKILL.md mixes both, which is confusing.
- Verify the Membrane CLI: the skill expects you to run 'npm install -g @membranehq/cli' but the registry did not list this required binary. Before installing, inspect the @membranehq/cli package on npm (check publisher, versions, and package contents) or install it in an isolated environment (container/VM) to limit risk.
- Understand the data flow: Membrane will proxy requests and hold auth for the target service. Any data you send via 'membrane request' or actions will transit Membrane's infrastructure. Only proceed if you trust Membrane (getmembrane.com) with that data.
- Interactive auth: the skill requires browser-based login flows; if you run in headless environments you'll use the printed URL + code flow — be ready for that.
- Ask for missing metadata: request that the skill manifest declare the required binary (membrane CLI) and link to a specific repository or package release so you can audit it. Having the registry include an install spec would remove a key inconsistency.
Given the mismatches (declared requirements vs SKILL.md) and the external-proxy behavior, treat this skill with caution and verify the Membrane CLI and publisher before granting it access or installing the CLI globally.Like a lobster shell, security has layers — review code before you run it.
latestvk97953qnf6v90wz7gcd3898jwn8475qd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.