Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
starchild-ai-agent avatar

Trade Simulator

  • 1 installs
  • 1 repo stars
  • Updated July 29, 2026
  • starchild-ai-agent/community-skills

Run multi-agent market scenario simulations with LLM-driven whale/market-maker/retail participants, cascade analysis, and post-sim interviews.

About

A skill that runs multi-agent market scenario analysis using the MiroFish swarm-intelligence architecture, simulating whale/market-maker/retail participants with LLM reasoning, cascade analysis, and post-simulation interviews. A developer or trader uses it to stress-test market scenarios behaviorally rather than with a spreadsheet.

  • Multi-agent market simulation on MiroFish swarm architecture
  • LLM-driven participant reasoning, cascade analysis, post-sim interviews

Trade Simulator by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #909 of 1,106 Finance & Trading skills by installs in the Skillselion catalog
  • Data as of Jul 30, 2026 (Skillselion catalog sync)
npx skills add https://github.com/starchild-ai-agent/community-skills --skill trade-simulator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars1
Last updatedJuly 29, 2026
Repositorystarchild-ai-agent/community-skills

What it does

Run multi-agent market scenario simulations with LLM-driven whale/market-maker/retail participants, cascade analysis, and post-sim interviews.

Files

SKILL.mdMarkdownGitHub ↗

🐟 Trade Simulator (MiroFish Architecture)

Multi-agent scenario analysis for traders. Not a spreadsheet — a behavioral simulation.
Built on MiroFish's swarm intelligence architecture, adapted from social simulation to market simulation.

MiroFish Integration

This skill implements MiroFish's 5-stage prediction pipeline, replacing social media environments with financial markets:

MiroFish StageOriginal (Social)Our Adaptation (Markets)
1. Graph ConstructionZep knowledge graph from news/docsMarket State Graph from live Coinglass/HL data
2. Environment SetupTwitter/Reddit agent profilesMarket participant profiles (Whale, MM, Retail, etc.)
3. SimulationOASIS dual-platform social interactionRound-based market interaction with LLM reasoning
4. Report GenerationReACT report with Zep toolsReACT report with market data tools
5. Deep InteractionInterview any social agentInterview any market participant

Key MiroFish Patterns Used

1. LLM-driven agent reasoning (from oasis_profile_generator.py) — agents don't use if/else rules. Each agent has a persona prompt and "thinks" each round via LLM call 2. Simulation config auto-generation (from simulation_config_generator.py) — describe scenario in natural language, LLM generates agent roster, parameters, event timeline, activity patterns 3. ReACT report generation (from report_agent.py) — multi-step reasoning with tool use: plan outline → generate sections → cite evidence → synthesize predictions 4. Post-simulation interviews (from zep_tools.py Interview system) — chat with any agent after simulation to understand their reasoning 5. Knowledge graph backbone — entities, relationships, and facts structured for agent retrieval (we use in-memory graph instead of Zep Cloud)

What We Don't Use

  • ❌ OASIS / camel-ai (social media simulation runtime — irrelevant to markets)
  • ❌ Zep Cloud (replaced with local in-memory knowledge graph)
  • ❌ Flask frontend (we output to agent conversation)
  • ❌ Twitter/Reddit environments (replaced with market environment)

Architecture

skills/trade-simulator/
├── SKILL.md                          # This file
└── scripts/
    ├── mirofish_engine.py            # Core engine — 5-stage pipeline
    ├── market_graph.py               # Stage 1: Market state graph builder
    ├── profile_generator.py          # Stage 2: LLM agent profile generation
    ├── simulation_runner.py          # Stage 3: Round-based market simulation
    ├── report_agent.py               # Stage 4: ReACT report generation
    └── interview.py                  # Stage 5: Post-sim agent interviews

Usage

Quick Scenario Analysis

Agent: "Run a trade simulation: What happens to my BTC short if ETF inflows spike 500%?"

The engine will: 1. Build market state graph from live data (OI, funding, liquidations, whale positions) 2. Auto-generate 5-8 market participant agents calibrated to current conditions 3. Run 6-round simulation where each agent LLM-reasons about their actions 4. Generate ReACT analysis report with turning points, cascade analysis, recommendations 5. Offer interactive interviews with any simulated agent

Supported Scenarios

  • Directional shocks: "What if BTC pumps/dumps 10-20%?"
  • Catalyst events: "What if ETF inflows spike?" / "What if Tether depegs?"
  • Market structure: "What if funding goes extreme?" / "What if OI doubles?"
  • Portfolio stress: "How does my portfolio react to a black swan?"

Interview Mode

After any simulation:

Agent: "Interview the whale agent — why did they cover at round 4?"
Agent: "Ask the market maker about their liquidity decision"

Data Sources (Live)

DataToolWhat It Feeds
Open Interestcg_open_interest()Market leverage state
Funding Ratesfunding_rate()Positioning sentiment
Liquidation Levelscg_liquidations()Cascade trigger points
Whale Positionscg_hyperliquid_whale_positions()Whale agent calibration
Long/Short Ratioslong_short_ratio()Crowd positioning
Orderbook Depthhl_orderbook()MM agent calibration
ETF Flowscg_btc_etf_flows()Institutional flow context
Price/OHLCcg_ohlc_history()Price context
Social Sentimentlunar_coin()Retail agent behavior

Workflow

1. Collect live market data using tools above 2. Run simulation: python3 skills/trade-simulator/scripts/mirofish_engine.py

  • Pass market data + scenario + user positions as JSON
  • Engine runs all 5 MiroFish stages
  • Returns structured results (agent actions, report, interview-ready state)

3. Present results with key insights, PnL impact, risk warnings 4. Offer interviews — user can interrogate any agent

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.