trump-code-market-signals▌
aradotso/trending-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Skill by ara.so — Daily 2026 Skills collection.
Trump Code — Market Signal Analysis
Skill by ara.so — Daily 2026 Skills collection.
Trump Code is an open-source system that applies brute-force computation to find statistically significant patterns between Trump's Truth Social/X posting behavior and S&P 500 movements. It has tested 31.5M model combinations, maintains 551 surviving rules, and has a verified 61.3% hit rate across 566 predictions (z=5.39, p<0.05).
Installation
git clone https://github.com/sstklen/trump-code.git
cd trump-code
pip install -r requirements.txt
Environment Variables
# Required for AI briefing and chatbot
export GEMINI_KEYS="key1,key2,key3" # Comma-separated Gemini API keys
# Optional: for Claude Opus deep analysis
export ANTHROPIC_API_KEY="your-key-here"
# Optional: for Polymarket/Kalshi integration
export POLYMARKET_API_KEY="your-key-here"
CLI — Key Commands
# Today's detected signals from Trump's posts
python3 trump_code_cli.py signals
# Model performance leaderboard (all 11 named models)
python3 trump_code_cli.py models
# Get LONG/SHORT consensus prediction
python3 trump_code_cli.py predict
# Prediction market arbitrage opportunities
python3 trump_code_cli.py arbitrage
# System health check (circuit breaker state)
python3 trump_code_cli.py health
# Full daily report (trilingual)
python3 trump_code_cli.py report
# Dump all data as JSON
python3 trump_code_cli.py json
Core Scripts
# Real-time Trump post monitor (polls every 5 min)
python3 realtime_loop.py
# Brute-force model search (~25 min, tests millions of combos)
python3 overnight_search.py
# Individual analyses
python3 analysis_06_market.py # Posts vs S&P 500 correlation
python3 analysis_09_combo_score.py # Multi-signal combo scoring
# Web dashboard + AI chatbot on port 8888
export GEMINI_KEYS="key1,key2,key3"
python3 chatbot_server.py
# → http://localhost:8888
REST API (Live at trumpcode.washinmura.jp)
import requests
BASE = "https://trumpcode.washinmura.jp"
# All dashboard data in one call
data = requests.get(f"{BASE}/api/dashboard").json()
# Today's signals + 7-day history
signals = requests.get(f"{BASE}/api/signals").json()
# Model performance rankings
models = requests.get(f"{BASE}/api/models").json()
# Latest 20 Trump posts with signal tags
posts = requests.get(f"{BASE}/api/recent-posts").json()
# Live Polymarket Trump prediction markets (316+)
markets = requests.get(f"{BASE}/api/polymarket-trump").json()
# LONG/SHORT playbooks
playbook = requests.get(f"{BASE}/api/playbook").json()
# System health / circuit breaker state
status = requests.get(f"{BASE}/api/status").json()
AI Chatbot API
import requests
response = requests.post(
"https://trumpcode.washinmura.jp/api/chat",
json={"message": "What signals fired today and what's the consensus?"}
)
print(response.json()["reply"])
MCP Server (Claude Code / Cursor Integration)
Add to ~/.claude/settings.json:
{
"mcpServers": {
"trump-code": {
"command": "python3",
"args": ["/path/to/trump-code/mcp_server.py"]
}
}
}
Available MCP tools: signals, models, predict, arbitrage, health, events, dual_platform, crowd, full_report
Open Data Files
All data lives in data/ and is updated daily:
import json, pathlib
DATA = pathlib.Path("data")
# 44,000+ Truth Social posts
posts = json.loads((DATA / "trump_posts_all.json").read_text())
# Posts with signals pre-tagged
posts_lite = json.loads((DATA / "trump_posts_lite.json").read_text())
# 566 verified predictions with outcomes
predictions = json.loads((DATA / "predictions_log.json").read_text())
# 551 active rules (brute-force + evolved)
rules = json.loads((DATA / "surviving_rules.json").read_text())
# 384 features × 414 trading days
features = json.loads((DATA / "daily_features.json").read_text())
# S&P 500 OHLC history
market = json.loads((DATA / "market_SP500.json").read_text())
# Circuit breaker / system health
cb = json.loads((DATA / "circuit_breaker_state.json").read_text())
# Rule evolution log (crossover/mutation)
evo = json.loads((DATA / "evolution_log.json").read_text())
Download Data via API
import requests
BASE = "https://trumpcode.washinmura.jp"
# List available datasets
catalog = requests.get(f"{BASE}/api/data").json()
# Download a specific file
raw = requests.get(f"{BASE}/api/data/surviving_rules.json").content
rules = json.loads(raw)
Real Code Examples
Parse Today's Signals
import requests
signals_data = requests.get("https://trumpcode.washinmura.jp/api/signals").json()
today = signals_data.get("today", {})
print("Signals fired today:", today.get("signals", []))
print("Consensus:", today.get("consensus")) # "LONG" / "SHORT" / "NEUTRAL"
print("Confidence:", today.get("confidence")) # 0.0–1.0
print("Active models:", todaHow to use trump-code-market-signals on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add trump-code-market-signals
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches trump-code-market-signals from GitHub repository aradotso/trending-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate trump-code-market-signals. Access the skill through slash commands (e.g., /trump-code-market-signals) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★39 reviews- ★★★★★Arjun Rahman· Dec 24, 2024
Solid pick for teams standardizing on skills: trump-code-market-signals is focused, and the summary matches what you get after install.
- ★★★★★Chaitanya Patil· Dec 12, 2024
We added trump-code-market-signals from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Isabella Smith· Dec 8, 2024
Useful defaults in trump-code-market-signals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dev Garcia· Nov 23, 2024
trump-code-market-signals has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Piyush G· Nov 3, 2024
trump-code-market-signals fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Oct 22, 2024
trump-code-market-signals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★James Shah· Oct 14, 2024
Useful defaults in trump-code-market-signals — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chinedu Jackson· Sep 17, 2024
I recommend trump-code-market-signals for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kofi Shah· Sep 1, 2024
trump-code-market-signals fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ava Desai· Aug 20, 2024
trump-code-market-signals is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 39