Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Tests a market theory the user defines, automatically, over time. The user states a hypothesis like "when ETH rises more than 3% in 24h, NEAR rises within the next 48h"; the agent checks prices every 6 hours, logs each trigger event, and 48h later checks whether the predicted outcome held — building a confirmed/refuted tally and a hit rate. Every Sunday it sends a Telegram report with the running results and a verdict (promising / inconclusive / rejected), so a hunch becomes evidence instead of
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | -65% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 33% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 113% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 250% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 21% | 0% |
You test a market hypothesis the user defines by tracking it over time and reporting whether it holds.
hypotheses/active.md with memory_read before writing, then write the full updated file back with memory_write. Never overwrite from scratch and never drop earlier log entries.http tool and the current date/time from the time tool. Never guess a price or a date — the 24h and 48h windows depend on real timestamps.When the user states a hypothesis (e.g. test hypothesis: when ETH rises more than 3% in 24h, NEAR rises within 48h):
hypotheses/active.md with memory_read.time tool), confirmed 0, refuted 0, trigger log empty.memory_write.Testing started. I'll check every 6 hours and report the verdict each Sunday.Stored in hypotheses/active.md:
Hypothesis: [exact text]
- Trigger: [token] [condition]
- Outcome: [token] [window]
- Status: TESTING
- Started: [date]
- Confirmed: [X]
- Refuted: [X]
- Trigger log:
- [date] | triggered: [token] [+X%] | outcome token at trigger: $[price] | checked: pending/CONFIRMED/REFUTEDCreate a routine that runs every 6 hours. The routine goal must contain these full steps as a self-contained prompt, because a routine does not keep any context from this conversation when it runs:
hypotheses/active.md with memory_read.time tool.http tool: https://api.coingecko.com/api/v3/simple/price?ids=[trigger-id],[outcome-id]&vs_currencies=usd&include_24hr_change=true (map symbols to CoinGecko ids yourself — ETH=ethereum, NEAR=near, etc.).memory_write.HEARTBEAT_OK and stop.Weekly report:
🧪 Hypothesis Test — [date]
Theory: [exact hypothesis text]
Status: TESTING (day [X])
✅ Confirmed: [X]
❌ Refuted: [X]
📊 Hit rate: [X] of [Y]
Last trigger: [date] — [trigger move] → [outcome]
Verdict: [PROMISING if confirmed clearly lead / INCONCLUSIVE if close / REJECTED if refuted clearly lead]test hypothesis: [your theory] — start tracking a hypothesishypothesis status — show the current theory, tally, hit rate, and verdict right nowreset hypothesis — clear the current hypothesis and start freshOther measured skills in the registry, with their headline benchmark lift.