Polymarket Market Importer
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent and disclosed, but it uses a Simmer API key, scheduled automation, and live account-import actions that users should configure carefully.
Install only if you are comfortable giving the skill a Simmer API key and, in live mode, letting it import matching markets automatically. Run it in dry-run mode first, keep filters and max_per_run conservative, protect the API key and imported_markets.json, and disable the cron schedule if you do not want recurring operation.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If live mode is enabled, matching markets can be imported automatically and may consume quota or alter the user's Simmer portfolio/import list.
Live mode calls the Simmer client to import a discovered market, which changes the user's Simmer account state. This matches the skill purpose and is bounded by filters and max_per_run, but it is still an automated account action.
if not dry_run: ... result = client.import_market(url)
Start with dry run, review keywords/categories/min_volume, keep max_per_run conservative, and enable --live only when you want automatic imports.
Anyone running the skill with this environment variable can use the configured Simmer account permissions available to that key.
The skill authenticates to Simmer using an API key from the environment. This is expected for importing markets and is disclosed, but it grants account access to the integration.
api_key = os.environ.get("SIMMER_API_KEY") ... _client = SimmerClient(api_key=api_key, venue=venue, live=live)Use a least-privileged or dedicated Simmer API key if available, store it securely, and rotate it if you uninstall or no longer trust the environment.
Installing later versions of the SDK may introduce changed behavior or dependency risk outside this skill's own files.
The skill depends on an external Python package without a pinned version. This is expected for the Simmer integration, but package changes could affect behavior.
"pip": ["simmer-sdk"]
Install from a trusted package index and consider pinning a known-good simmer-sdk version in your environment.
Local access to the skill directory can reveal what markets were imported, and editing the file can affect which markets are skipped or re-imported.
The skill persists imported market IDs, questions, and timestamps locally and reuses that file to skip already-seen markets. This is purpose-aligned but records user market interests and influences future runs.
SEEN_FILE = Path(__file__).parent / "imported_markets.json" ... "question": question, "imported_at": datetime.now(timezone.utc).isoformat()
Keep the skill directory private, avoid syncing the state file to places you do not trust, and delete or edit imported_markets.json only when you intentionally want to reset deduplication.
After scheduling/live configuration, the importer may keep checking and importing matching markets every six hours.
The skill is intended to run repeatedly on a schedule. This is disclosed and autostart is false, but users should understand that enabling the schedule allows ongoing automated activity.
"cron": "0 */6 * * *", "autostart": false, "automaton": {"managed": true, "entrypoint": "market_importer.py"}Confirm the cron schedule before enabling live use, and disable or remove the schedule when you no longer want recurring imports.