- Home
- Skills
- Trading & Investing
- time of day edge finder
time of day edge finder
Identifies profitable trading windows and filters out high-noise sessions using historical trade data.
$5
Works with the AI Agents you already use
time of day edge finder
Example session with this skill installed
Analyze these trade logs from my ES futures strategy. Identify which hours are profitable and which are just adding noise. Use a minimum of 20 trades per bucket.
- Read your context and instructions
- Compiled the time of day
Session Edge Summary
BEST: RTH 10:00-11:00 (Avg +0.38, Sharpe 2.1, 45 trades)
WORST: Lunch 12:00-13:00 (Avg -0.12, PF 0.82, 30 trades)
NOISY: Post-Market (Std 2.4, Avg +0.05, 12 trades)
=> Recommendation: Focus on RTH 10:00-11:00. Cease trading during Lunch and Post-Market.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Intraday strategies often bleed profits during specific hours due to low liquidity or erratic volatility. Relying on aggregate performance data masks these toxic windows, leading to unnecessary drawdowns.
What it does
- Partitions trade logs into hourly and session-based buckets to isolate performance variance.
- Calculates noise-to-edge ratios to distinguish between lucky streaks and statistically stable windows.
- Flags buckets with insufficient sample sizes to prevent over-optimization on sparse data.
- Generates actionable participation schedules, explicitly identifying hours to trade or avoid.
Frameworks & tools
Designed for integration with pandas and numpy. Compatible with any CSV or JSON trade log containing standard timestamps.
Why this beats prompting it yourself
Standard LLM prompts often fail to account for the noise-to-signal ratio, confusing high variance with actual edge. This skill implements a systematic filtering logic that treats low-sample or high-volatility hours as un-tradeable by default.
Use cases
- Optimizing algorithmic execution windows to avoid high-slippage lunch hours.
- Refining manual trading plans by identifying personal performance peaks during specific sessions.
- Filtering backtest results to remove sessions that exhibit non-stationary behavior.
Known limitations
Requires a minimum trade count per bucket to ensure statistical relevance. Analysis is historical and does not predict performance shifts caused by changing market regimes.
Requires trade logs with precise timestamps. Minimum bucket sizes are enforced to prevent overfitting. Does not account for sudden structural market changes.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Requires
Permissions
No special permissions declared or detected