Simmer Signal Service
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill mostly matches a paid trading-signal service, but its price is inconsistent and it encourages automated repeated paid calls, so billing should be reviewed carefully.
Before installing, verify the exact SkillPay charge amount, which SkillPay skill ID receives payment, and whether any cron job will run automatically. Avoid enabling five-minute scheduled runs unless you set a spending limit and are comfortable with repeated paid trading signals.
Findings (4)
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.
Users may misunderstand the actual cost per signal, especially if the skill is run repeatedly.
The user-facing documentation advertises 0.001 USDT in some places but 0.01 USDT in others, creating a material billing ambiguity for a paid skill.
“only 0.001 USDT per signal” ... “每次调用 1 token = 0.001 USDT” ... “用户每获取一次信号 → 自动扣 0.01 USDT”
Use one authoritative price everywhere, align the code/config/docs, and show the exact charge before each paid signal.
A user could accumulate repeated charges and receive automated trading recommendations without reviewing each run.
The recommended workflow is persistent every-five-minute execution of a paid call, framed around continuous developer revenue, with no documented spending cap or confirmation step.
“OpenClaw Cron（推荐）” ... “--cron "*/5 * * * *"” ... “用户 24 小时不间断调用 → 你 24 小时不间断收钱”
Add explicit opt-in for scheduled billing, spending limits, rate limits, and clear instructions for disabling the cron job.
The user should know exactly which billing account and skill ID will be used before providing credentials.
The skill uses a SkillPay API key for billing and has a default SkillPay skill ID; this is related to the stated paid-service purpose but is high-impact account authority.
SKILLPAY_API_KEY = os.getenv("SKILLPAY_API_KEY") ... SKILLPAY_SKILL_ID = ... "63f0b52e-50fe-4234-a22b-d2d5dd978e1a" ... "Authorization": f"Bearer {SKILLPAY_API_KEY}"Clearly document the SkillPay credential scope, skill ID, recipient, and amount charged; users should use limited-scope credentials if available.
Dependency behavior can change over time depending on the installed version.
The dependency is not pinned to an exact version. This is common for simple API clients, but it means future installs may resolve to different package versions.
requests>=2.28.0
Pin dependency versions or install in a trusted, isolated environment.