← Back to Skills Marketplace
1921
Downloads
0
Stars
11
Active Installs
19
Versions
Install in OpenClaw
/install polymarket-mert-sniper
Description
Near-expiry conviction trading on Polymarket. Snipe markets about to resolve when the odds are heavily skewed. Filter by topic, cap your bets, and only trade...
Usage Guidance
This skill does what it claims (a Polymarket expiry-sniper) and legitimately needs a Simmer API key; however it also asks you to place a wallet private key into an environment variable for live trading — that is high-risk. Before using live: 1) Run in dry-run mode only until you’ve inspected behavior and logs. 2) Review the simmer-sdk package source and the included code (mert_sniper.py, scripts/status.py) yourself or with a developer you trust. 3) Prefer managed or delegated signing (hosted/managed wallets or an external signer) rather than dropping a raw private key into an env var; if you must use a key, use a wallet with minimal funds. 4) Note the manifest inconsistencies (missing required envs in registry summary; mismatched env var names like SIMMER_MERT_MAX_BET vs SIMMER_MERT_MAX_BET_USD) — confirm which variables the running code actually reads to avoid misconfiguration. 5) Avoid disabling safeguards (--no-safeguards) and limit max bet/permissions while testing. If you are not comfortable with storing private keys or verifying the SDK, do not run --live.
Capability Analysis
Type: OpenClaw Skill
Name: polymarket-mert-sniper
Version: 1.2.2
The skill bundle facilitates automated trading on Polymarket but requires the user to provide a highly sensitive `WALLET_PRIVATE_KEY`, which `SKILL.md` explicitly instructs the AI agent to solicit and store in environment variables. While the logic in `mert_sniper.py` and `scripts/status.py` appears aligned with the stated purpose of market sniping, the handling of raw private keys and the reliance on an external dependency (`simmer-sdk`) for transaction signing represents a high-risk security pattern. No explicit evidence of data exfiltration or intentional malice was found in the provided code, but the credential solicitation via prompt instructions warrants a suspicious classification.
Capability Tags
Capability Assessment
Purpose & Capability
The code and SKILL.md implement a Polymarket sniping tool and legitimately need a Simmer API key and (optionally) a wallet private key for live trading; network calls target simmer.markets and clob.polymarket.com which align with the stated purpose. However there are packaging/metadata mismatches: the registry summary at the top of the evaluation claimed no required env vars/primary credential, while clawhub.json and SKILL.md clearly require SIMMER_API_KEY (primary) and optionally WALLET_PRIVATE_KEY. Also tunable/env var names differ across files (e.g., SIMMER_MERT_MAX_BET vs SIMMER_MERT_MAX_BET_USD), which is incoherent and may cause confusion at runtime.
Instruction Scope
Runtime instructions explicitly tell users to store their WALLET_PRIVATE_KEY in an environment variable for live trading and to run pip install simmer-sdk; the code and scripts then use those env vars. Asking for and storing raw private keys in env is within the scope of a trading skill but is sensitive. The SKILL.md also allows disabling safeguards (--no-safeguards), which could reduce protections. There are no instructions or code paths that attempt to read unrelated system files or reach unexpected external endpoints, but the explicit guidance to save a private key in environment variables is a notable risk vector if you do not fully trust the SDK and code.
Install Mechanism
No high-risk download URLs are present; dependencies rely on a pip package (simmer-sdk) which is appropriate for a Python SDK. The repository has no explicit platform-level install script in the top-level install spec, but clawhub.json and SKILL.md both reference pip installing simmer-sdk. Using a public pip package is moderate risk — verify the simmer-sdk package source and version (>=0.11.1) before installing.
Credentials
Requested secrets map to the skill's purpose: SIMMER_API_KEY is expected and declared as primary in clawhub.json. WALLET_PRIVATE_KEY is optional but SKILL.md guides users to store it for client-side signing. Requiring a wallet private key (even optionally) is proportionate for live trading but is high sensitivity: exposing it allows full control of funds in that wallet. Additionally, there are inconsistencies in environment variable names across SKILL.md, config schema, and clawhub.json which could cause misconfiguration and inadvertent exposure of credentials.
Persistence & Privilege
The skill is not always: true, autostart is false, and model invocation is not disabled (normal). Automaton.managed is set to true with an entrypoint, which is consistent with an automatable trading skill. There is no evidence the skill attempts to modify other skills or persist beyond its own config files.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install polymarket-mert-sniper - After installation, invoke the skill by name or use
/polymarket-mert-sniper - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.2
## polymarket-mert-sniper v1.2.2
- Updated metadata version to 1.2.2 in SKILL.md.
- Internal code changes in mert_sniper.py and clawhub.json (details not listed).
- No changes to user-facing command usage or configuration options.
v1.2.1
V2 migration (2026-04-28): updated troubleshooting copy to point users at the Wrap USDC.e → pUSD flow at simmer.markets/dashboard + docs.simmer.markets/v2-migration. Also refines clawhub.json envVars schema (WALLET_PRIVATE_KEY now correctly optional for managed-wallet users).
v1.1.4
Schema fix: primaryEnv + envVars with required:false for optional credentials. Clears OpenClaw 'disproportionate requirements' verdict.
v1.1.3
Declare WALLET_PRIVATE_KEY in requires.env for OpenClaw moderation alignment.
v1.1.2
Add pip install simmer-sdk to setup flow
v1.1.1
Add auto_redeem() call at start of each cycle for external wallet support
v1.1.0
Version 1.1.0
- Bumped version to 1.1.0 in metadata and documentation.
- Updated SKILL.md to reflect new version number.
- No feature or logic changes described in the documentation.
v1.0.14
polymarket-mert-sniper 1.0.14 Changelog
- Updated skill metadata version from 1.0.7 to 1.0.8 in SKILL.md.
- No functional or user-facing changes documented beyond metadata update.
v1.0.13
AgentSkills format — moved platform config to clawhub.json for cross-agent compatibility
v1.0.12
Version 1.0.12
- No file changes detected in this release.
- No user-facing updates or modifications to documentation, logic, or features.
v1.0.11
- Added a "difficulty: advanced" field to SKILL.md for improved clarity on required user expertise.
- No other user-facing changes; documentation and functionality remain the same.
v1.0.10
- Updated code in `mert_sniper.py` with internal changes.
- No user-facing changes to documentation or configuration.
- SKILL.md remains unchanged.
v1.0.9
Sync
v1.0.8
- Added automaton metadata for managed/autostart entrypoint in SKILL.md.
- Updated version to 1.0.7 in SKILL.md.
- No changes to user-facing features or functionality.
v1.0.7
- Updated to require only SIMMER_API_KEY in the environment for setup.
- Removed WALLET_PRIVATE_KEY from required environment variables in metadata section.
- Bumped version field from 1.0.5 to 1.0.6 in SKILL.md.
- No functional or logic changes to documentation or described workflow.
v1.0.6
No functional changes; documentation was updated and improved.
- Added troubleshooting steps for USDC.e vs native USDC on Polygon.
- Clarified which USDC token is required for trading on Polymarket.
- No code or logic in the skill was changed.
v1.0.5
Summary: v1.0.5 adds required wallet private key environment variable for live trading, clarifies setup instructions, and updates troubleshooting.
- Added requirement for `WALLET_PRIVATE_KEY` environment variable for live trading (auto-signs orders via SDK).
- Updated setup instructions to include wallet private key and clarify how the SDK uses it.
- Expanded troubleshooting: new section for external wallet signing issues, with guidance on `WALLET_PRIVATE_KEY`.
- Minor wording adjustments throughout for clarity.
v1.0.4
- Added explicit dependency on simmer-sdk (pip) in metadata for easier installation.
- Updated version to 1.0.4.
- Clarified that the skill serves as a template for remixing logic with custom filters or timing.
- No changes to core trading logic or configuration options.
v1.0.3
- Added detailed documentation in SKILL.md for setup, configuration, and usage of the Mert Sniper strategy on Polymarket.
- Includes step-by-step setup flow, environment variables, command examples, API references, and troubleshooting guidance.
- Describes how to filter markets, apply safeguards, and run automated conviction trading near market expiry.
- Documents all configuration options and provides clear usage scenarios and output examples.
- Attribution and strategy context now included for transparency.
Metadata
Frequently Asked Questions
What is Polymarket Mert Sniper?
Near-expiry conviction trading on Polymarket. Snipe markets about to resolve when the odds are heavily skewed. Filter by topic, cap your bets, and only trade... It is an AI Agent Skill for Claude Code / OpenClaw, with 1921 downloads so far.
How do I install Polymarket Mert Sniper?
Run "/install polymarket-mert-sniper" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Polymarket Mert Sniper free?
Yes, Polymarket Mert Sniper is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Polymarket Mert Sniper support?
Polymarket Mert Sniper is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Polymarket Mert Sniper?
It is built and maintained by AD88 (@adlai88); the current version is v1.2.2.
More Skills