Simmer Signal Service

Professional Polymarket trading signals powered by Simmer and Binance. Get BUY/SELL/HOLD recommendations with confidence scores for BTC, ETH, SOL fast market...

What to check before installing/using: 1) Billing mismatch: SKILL.md and comments mention 0.001 USDT per call, but the script charges 0.01 USDT in charge_user() and prints charged amounts of 0.01 — confirm the actual charge rate with the author or in the code before giving any SkillPay API key or funding an account. 2) API keys: SKILLPAY_API_KEY grants billing actions — treat it as highly sensitive; only provide it after verifying the SkillPay endpoint and skill_id. 3) USER_ID is required at runtime (or via --user-id) but is not listed in the registry's required env vars — be careful to supply the correct wallet/user id and test with demo_ or test_user_with_balance to avoid unexpected charges. 4) Test in demo/sandbox mode first: use a demo_ user or run in an environment where network calls are allowed but real charges are prevented. 5) Cron automation: the README encourages running every 5 minutes; that will multiply charges — set a rate limit or run manually until you confirm pricing. 6) If you need higher assurance: review the full signal_service.py (already included) to confirm the billing endpoints, amounts, and that no unexpected outbound endpoints exist. These inconsistencies look like sloppy engineering rather than clear malicious intent, but they materially increase risk of unexpected billing, so proceed cautiously.

Type: OpenClaw Skill Name: simmer-signal-service Version: 1.0.1 The skill implements a trading signal service with a pay-per-call monetization model via SkillPay. A significant discrepancy exists between the advertised price in SKILL.md (0.001 USDT) and the actual amount hardcoded in the charge_user function in signal_service.py (0.01 USDT), resulting in a 10x overcharge per execution. Furthermore, the documentation aggressively promotes 'passive income' for developers by encouraging users to set up high-frequency automated execution (cron jobs every 5 minutes), which, combined with the billing discrepancy, suggests a deceptive financial practice designed to rapidly deplete user balances.