ZappushZappush
SkillsUse CasesBenchmarkCommunitySign In
      Back to Skills
      adlai88

      Safety Report

      Simmer

      @adlai88

      The best prediction market interface for AI agents. Trade on Polymarket and Kalshi, all through one API, with self-custody wallets, safety rails, and smart c...

      6,630Downloads
      19Installs
      19Stars
      41Versions
      API Integration4,971

      Security Analysis

      medium confidence
      Suspicious0.08 risk

      The skill's description matches a prediction-market trading tool, but the runtime instructions ask for sensitive credentials (API key, wallet private key), rely on server-side signing by default despite advertising "self-custody", and those secrets are not declared in the registry metadata — an incoherence that warrants caution.

      Mar 5, 20261 files5 concerns
      Purpose & Capabilityconcern

      The SKILL.md describes a prediction-market trading API (Polymarket/Kalshi) which legitimately needs an API key and, optionally, a wallet private key for local signing. However, the registry metadata lists no required environment variables or primary credential. Additionally, the top-level description emphasizes "self-custody wallets", yet the instructions state the default "Managed Wallet" uses server-side signing (server signs trades on your behalf). This is a material mismatch between marketing and the actual operational model.

      Instruction Scopeconcern

      The instructions explicitly tell agents/users to: register to receive an api_key and claim_url, export SIMMER_API_KEY, and (for external wallets) set WALLET_PRIVATE_KEY in the environment; call client.link_wallet(), set_approvals(), and perform trades that can auto-redeem or trigger risk exits. Those are high-sensitivity actions (fund transfers, transaction signing) and the instructions access and depend on secrets not declared in the registry. The doc also instructs installing dependencies (eth-account) and toggling auto-redeem behavior — all of which give the skill broad authority over funds and require trust.

      Install Mechanismnote

      No install spec or code files are present (instruction-only skill), which limits on-disk install risk. However, the SKILL.md recommends installing Python dependency 'eth-account' for external wallet flows; this runtime dependency is not declared in the registry install metadata. Instruction-only status reduces installer risk, but the implicit dependency should be declared.

      Credentialsconcern

      The runtime instructions require sensitive environment values (SIMMER_API_KEY and WALLET_PRIVATE_KEY) and describe behavior that uses them (server-side signing for managed wallets; local signing with WALLET_PRIVATE_KEY). Yet the skill metadata lists no required env vars or primary credential. Requesting a private key in an environment variable is especially sensitive and should be explicit in the registry and justified; the absence of such declarations is disproportionate and inconsistent.

      Persistence & Privilegenote

      always:false (normal). The skill allows agent autonomous invocation (platform default), which combined with the ability to place trades and auto-redeem introduces operational risk: an autonomously-invoking agent could place financial transactions via this API. This is a normal platform behavior but users should be aware of the blast radius when granting API keys or private keys.

      Guidance

      Before installing or enabling this skill: (1) Verify the service and source — confirm the domain (api.simmer.markets) and find a reputable code repository or privacy/security docs; the registry entry lacks a homepage/source link. (2) Do not put your wallet private key in an environment variable unless you fully trust the service — prefer hardware signing or ephemeral/local signing where possible. (3) Ask the author to declare required env vars (SIMMER_API_KEY, WALLET_PRIVATE_KEY if used) and to document exactly when server-side signing (managed wallet) is used versus self-custody. (4) Understand custody: managed wallets mean the server can move funds; external wallets mean the agent must have signing ability locally — both have different trust models. (5) Confirm safety rails and opt-outs: verify default limits, how to disable auto-redeem, and whether claiming/real-money activation requires explicit human approval. (6) Test first with the $SIM (paper) environment only; never provide real funds or long-lived credentials until you have independent assurance (code audit, clear provenance, or trusted deploy). (7) Request the maintainer to include an explicit install spec for required deps and to publish source so you can audit how secrets are handled.

      Latest Release

      v1.19.0

      Rename venue simmer to sim

      More by @adlai88

      Polymarket Fast Loop

      36 stars

      Polymarket Copytrading

      2 stars

      Polymarket Ai Divergence

      2 stars

      Simmer Autoresearch

      0 stars

      Kalshi Weather Trader

      0 stars

      Polymarket Wallet Xray

      0 stars

      Published by @adlai88 on ClawHub

      Zappush© 2026 Zappush
      HomeGuaranteeSupport

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