seasonal-calendar-effects

Generate long, short, or neutral trading signals from month and weekday effects on OHLCV data.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/loanntc/Paave --skill seasonal-calendar-effects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seasonal-calendar-effects
Source: https://github.com/loanntc/Paave/tree/main/skills/seasonal
Command: npx skills add https://github.com/loanntc/Paave --skill seasonal-calendar-effects

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, numpy, and includes scripts (resource) components.

What problem does it solve?

Markets often exhibit recurring time-based behaviors, but manually translating month/week seasonal tendencies into consistent trade signals is slow and error-prone.

Core Features & Use Cases

  • Month-effect signal generation: Produces long (+1), short (-1), or flat (0) decisions based on whether each bar’s month is configured as bullish or bearish.
  • Optional weekday overlay: Adds Monday/Friday (or any weekday list) effects and applies a combined-confirmation rule so trades only occur when month and weekday agree.
  • Use case: Backtest an equity or crypto strategy that targets the “spring rally” (Jan–Mar) and “sell in May” (May–Oct) effects using any OHLCV timeframe.

Quick Start

Run the seasonal-calendar-effects SignalEngine on your OHLCV DataFrame(s) to generate a per-bar signal series indicating long, short, or neutral positions.

Frequently Asked Questions about seasonal-calendar-effects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate trading signals from seasonal calendar effects in OHLCV data?

To generate trading signals from seasonal calendar effects, you process OHLCV datasets using pandas-based datetime indexing to map month-of-year and optional day-of-week regularities into long, short, or neutral position outputs.

What is the best way to backtest a "sell in May" seasonality strategy?

Backtesting a "sell in May" seasonality strategy involves configuring specific bullish and bearish months on your OHLCV DataFrame to produce deterministic long, short, or flat signals for your historical market analysis.

Can I combine month-of-year and day-of-week effects into a single trading signal?

Yes, you can combine month-of-year and day-of-week effects by applying a combined-confirmation rule that outputs a trade signal only when both the configured month and weekday conditions agree.

Do I need pandas and numpy to apply time-series seasonality patterns to my trading strategy?

Yes, you need pandas and numpy because the signal generation engine requires pandas-based datetime indexing to process OHLCV time-series data and apply the configured seasonal calendar rules.

What are the limitations of using calendar regularities for backtesting financial time-series?

Using calendar regularities for backtesting treats temporal seasonality as the primary hypothesis, meaning it outputs deterministic signals based solely on configured dates without incorporating fundamental market analysis or external volatility drivers.

Does seasonal-calendar-effects work with crypto OHLCV datasets for signal generation?

Yes, seasonal-calendar-effects works with any OHLCV dataset including crypto markets, applying configurable bullish and bearish month or weekday rules to generate deterministic time-series trading signals.