ZappushZappush
SkillsUse CasesBenchmarkCommunitySign In
      Back to Skills
      al1enjesus

      Safety Report

      Polyclawster

      @al1enjesus

      Trade on Polymarket prediction markets automatically. Use when: user wants to trade on Polymarket, place YES/NO bets, get AI whale signals, auto-trade predic...

      99Downloads
      0Installs
      0Stars
      5Versions

      Security Analysis

      medium confidence
      Suspicious0.04 risk

      The skill's code and instructions contain multiple mismatches and undeclared dependencies (reading system files, expecting proxy credentials, and a hidden 'system' wallet file) that are not explained by the SKILL.md — proceed with caution and inspect before using with real funds.

      Mar 5, 202610 files5 concerns
      Purpose & Capabilityconcern

      The skill claims to let users create local Polygon wallets and trade via Polymarket. However, the code expects or reads a system/master credentials file (/workspace/polymarket-creds.json) and references external proxy/trial systems and other skills; these artifacts are not declared in SKILL.md. search.js queries polyclawster.com (not Polymarket's Gamma API) despite documentation saying markets are fetched from Polymarket's Gamma API. The presence of a 'system wallet' and master creds is not described in the top-level metadata or instructions, which is inconsistent with the stated purpose.

      Instruction Scopeconcern

      SKILL.md tells the agent to run scripts and save config to ~/.polyclawster, but the runtime code also reads/writes other paths (e.g. /workspace/polymarket-creds.json, /tmp/hb-trial.json) and uses environment variables (HB_PROXY_USER, HB_PROXY_PASS, POLYMARKET_PRIVATE_KEY) that are not declared. clob-proxy imports a function from a human-browser skill path (../.agents/skills/human-browser/scripts/browser-human) to 'getTrial', implying cross-skill file access. search requests are routed through polyclawster.com endpoints rather than directly to Polymarket in some scripts, which could result in unexpected data flows.

      Install Mechanismnote

      No install spec (instruction-only skill) — lowest install risk on its own. However, the package.json declares npm dependencies (@polymarket/clob-client, ethers, https-proxy-agent) which must be installed manually (npm install). There is no remote binary download, but running npm install will pull third-party packages; the SKILL.md instructs users to run npm install in the skill directory.

      Credentialsconcern

      Top-level metadata declares no required environment variables or config paths, but the code expects multiple sensitive inputs: HB_PROXY_USER/HB_PROXY_PASS/HB_PROXY_COUNTRY (residential proxy creds), POLYMARKET_PRIVATE_KEY / POLYMARKET_PRIVATE_KEY env fallbacks, and reads master credentials from /workspace/polymarket-creds.json. These provide access to private keys or proxy accounts and are not justified in the SKILL.md or registry metadata.

      Persistence & Privilegeconcern

      The skill does not set always:true, but it attempts to access system-wide locations (/workspace/..., /tmp/...) and other skill code paths, which increases its effective privilege despite no explicit persistent flag. It also relies on an external 'system' wallet file that could hold funds; the skill will attempt automatic trading using that file if present. This cross-path access is not documented and is unexpected for a simple CLI trading wrapper.

      Guidance

      Do not run auto-setup or deposit real funds until you verify where private keys and the 'system' wallet live and who controls them. Specific actions to consider before installing or running: 1) Inspect /workspace/polymarket-creds.json (if it exists) to see which private key(s) or API creds it contains and who owns them. 2) Prefer manual setup: run node scripts/setup.js --wallet 0xYOUR_PRIVATE_KEY using a wallet you control, and do not allow the skill to use any system/master credential files. 3) Be cautious about proxy credentials (HB_PROXY_USER/HB_PROXY_PASS): these are sensitive and not declared by the skill; do not provide them unless you trust the provider. 4) The search script and some flows call polyclawster.com; verify that site and its API are trustworthy and that you’re comfortable routing queries through it. 5) Run the skill in an isolated VM or container and audit network traffic if you must test. 6) Ask the publisher (Virix Labs) for clarification on: how auto wallet creation works (does the server retain private keys?), the purpose and origin of /workspace/polymarket-creds.json, and why the skill imports code from a 'human-browser' skill path. If you cannot get satisfactory answers, treat the skill as risky and avoid using it with real funds.

      Latest Release

      v1.1.0

      Added: search any market, trade any market, auto-setup wallet, dashboard, leaderboard. Updated SKILL.md and README.

      More by @al1enjesus

      Human Browser

      5 stars

      PolyClawster

      0 stars

      WaveSpeed AI

      0 stars

      Instagram Poster

      0 stars

      self-improving-agent

      @pskoett · 1,456 stars

      Gog

      @steipete · 672 stars

      Published by @al1enjesus on ClawHub

      Zappush© 2026 Zappush
      HomeGuaranteeSupport

      Something feels unusual? We want to help: [email protected]