Kalshi Fed Temporal Mono Trader
PassAudited by ClawScan on May 10, 2026.
Overview
This is a disclosed dry-run-by-default trading skill, but live use requires high-value trading and wallet credentials, so users should treat it like a real-money trading bot.
Install only if you are comfortable with real-money trading automation. Start in dry-run mode, review the simmer-sdk dependency, use a dedicated low-balance wallet and API key, and do not enable --live or scheduling until you have verified the configured risk limits.
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 run with --live, the agent can spend real USDC according to the configured strategy and limits.
The skill can place real-money trades when live mode is explicitly selected.
`python trader.py --live` | Live (Kalshi via DFlow) | Real USDC
Run dry-runs first, review the markets and parameters, and only use --live with funds you are prepared to risk.
A compromised API key or private key could lead to unauthorized trades or wallet loss outside this skill's intended behavior.
The skill declares credentials that can authorize trading and access wallet funds.
`SIMMER_API_KEY` | Yes | Trading authority. Treat as a high-value credential. ... `SOLANA_PRIVATE_KEY` | Yes | Base58-encoded Solana private key for live trading.
Use a dedicated low-balance wallet and restricted API key if possible; never reuse a primary wallet private key.
The external SDK may handle trading requests and credentials, so its integrity matters for safe live use.
The skill relies on an external Python package for its trading integration.
"pip": [ "simmer-sdk" ]
Review the SDK source and package provenance before providing live credentials, and consider pinning a reviewed version.
Users may underestimate practical trading risk if they rely on the marketing language alone.
The strategy description uses strong certainty language even though live trading still has execution, liquidity, slippage, and market risks.
**Mathematical certainty** ... **No model risk** ... violations are temporary mispricings that must converge
Treat the strategy as risky financial automation despite the stated invariant, and validate assumptions with small dry-runs.
If the user later enables automation, the trading logic may run repeatedly without manual invocation.
The skill is prepared for managed automation, but the artifacts show it is not scheduled or autostarted by default.
"cron": null, "autostart": false, "automaton": { "managed": true, "entrypoint": "trader.py" }Keep automation disabled until dry-run behavior is verified; if enabling it, confirm it remains in dry-run unless live trading is intended.