Commodity Futures Skewness-Based Long-Short Monthly Strategy
Log in to collectAcademic paper
Commodities as Lotteries: Skewness and the Returns of Commodity Futures
Adrián Fernández-Pérez; Bart Frijns; Ana-Marı́a Fuertes; Joëlle Miffre
Auckland University of Technology
Open University of the Netherlands
Open University of the Netherlands - School of Management
City, University of London
Bayes Business School, City, University of London
Audencia Business School
Strategy in a nutshell
The investment universe consists of 27 futures contracts on commodities. Each month, investor calculates skewness (3rd moment of returns) from daily returns from data going 12 months into the past for all futures. Commodities are then sorted into quintiles and investor goes long quintile containing the commodities with the 20% lowest total skewness and short quintile containing the commodities with the 20% highest total skewness (over a ranking period of 12 months). The resultant portfolio is equally weighted and rebalanced each month.
Economic rationale
Academic studies explain skewness effect in all assets by investors are willing to pay a higher price, and to earn a lower expected return, on assets with lottery-like payoffs. A recent study shows that skewness affects commodity futures returns and documents that skewness is priced in different markets than the ones where retail investors typically trade. Hence, its findings suggest that the effect of skewness on asset returns is not merely a consequence of retail investor preferences. Rather this indicates that other groups of traders have these heterogeneous preferences.
Entry & exit
Entry
On each month, make_on_day sets target weights for GLD, SLV, DBC, GSG, USO, UNG, DBA. Read engine.set_target_weights in the lab code for the exact signal.
Exit
A name is exited when its target weight is set to 0 (or the whole dict is empty = cash). Fills use 5 bps commission and 2 bps slippage.
Market data required
Needs at least 60 adjusted daily closes on GLD, SLV, DBC, GSG, USO, UNG (+1 more) before the first signal is ready. ETF columns print on exchange sessions only. The lab loads Yahoo Finance via backtest.data.load_daily_prices.
Symbols
GLD, SLV, DBC, GSG, USO, UNG, DBA
Frequency
Monthly · Daily adjusted close; signals rebalance on the month change (last available session)
History needed
≥ 60 trading days per symbol (about 3 months), plus a few extra bars so the first signal can fire.
Fields
- Adjusted close (Yahoo auto_adjust)
- Session date index
Credentials
- None for paper and the onsite lab
- Broker or exchange API keys only for live orders
APIs & providers
Quant Buffet Data API
The lab calls load_daily_prices for the ASSETS panel of adjusted closes, then caches CSV so backtests replay the same series.
- Provider
- backtest.data.load_daily_prices
- Auth
- None for paper / sandbox backtests
- Endpoints
- load_daily_prices(ASSETS, start="2000-01-01")
Yahoo Finance via yfinance
US equities and ETFs, adjusted OHLCV, free for research (rate limits apply).
- Provider
- yfinance → Yahoo Finance
- Auth
- None for public history
- Endpoints
- Ticker.history / yf.download(auto_adjust=True)
Onsite backtest IDE
Quant Buffet native backtest IDEEdit and run Quant Buffet Python for Commodity Futures Skewness-Based Long-Short Monthly Strategy in the browser. Results update live with equity, drawdown, and metrics charts. Allowed: backtest.data, backtest.engine, backtest.metrics, numpy, pandas. Define ASSETS and make_on_day(prices). Shortcut: Ctrl+Enter. API docs →
Quant Buffet syntax cheat sheet (copy / insert)
Paste these fragments into the editor. The sandbox rejects QuantConnect, os, and network libraries.
from __future__ import annotations
import numpy as np
import pandas as pd
from backtest.data import load_daily_prices
from backtest.engine import EngineConfig, PortfolioEngine
from backtest.metrics import compute_metricsASSETS = ["SPY", "QQQ", "TLT", "GLD", "BIL"]def make_on_day(prices: pd.DataFrame):
cols = [c for c in ASSETS if c in prices.columns]
sma = prices[cols].rolling(200, min_periods=200).mean()
state = {"last": None}
def on_day(engine: PortfolioEngine, dt: pd.Timestamp) -> None:
if sma.loc[dt].isna().all():
return
key = (dt.year, dt.month)
if state["last"] == key:
return
state["last"] = key
long = [
s for s in cols
if pd.notna(prices.at[dt, s]) and pd.notna(sma.at[dt, s])
and prices.at[dt, s] > sma.at[dt, s]
]
weights = {} if not long else {s: 1.0 / len(long) for s in long}
engine.set_target_weights(dt, weights)
ready = sma.dropna(how="all").index.min() if sma.notna().any().any() else None
return on_day, readyengine.set_target_weights(dt, {"SPY": 0.60, "BIL": 0.40})Live backtest performance
Order records
Export to your platform
Transform Quant Buffet lab code (ASSETS + make_on_day / PortfolioEngine) into native classes for a third-party IDE — then copy and paste.
# Generated from Quant Buffet → QuantConnect LEAN
# Strategy: Commodity Futures Skewness-Based Long-Short Monthly Strategy
# Detected pattern: Custom / hybrid
# Source uses Quant Buffet lab APIs (ASSETS + make_on_day / PortfolioEngine).
# Review fees, data, and risk before live trading — educational export only.
from AlgorithmImports import *
class QuantBuffetExport(QCAlgorithm):
def Initialize(self):
self.SetStartDate(2010, 1, 1)
self.SetCash(100000)
tickers = ["GLD", "SLV", "DBC", "GSG", "USO", "UNG", "DBA"]
self.symbols = []
for t in tickers:
if "-" in t: # crypto proxy e.g. BTC-USD
self.symbols.append(self.AddCrypto(t.replace("-USD", ""), Resolution.Daily).Symbol)
else:
self.symbols.append(self.AddEquity(t, Resolution.Daily).Symbol)
self.Schedule.On(
self.DateRules.MonthStart(self.symbols[0]),
self.TimeRules.AfterMarketOpen(self.symbols[0], 30),
self.Rebalance,
)
# Logic: Custom Quant Buffet logic — adapt the signal block to match your lab on_day().
def Rebalance(self):
# Pattern: custom — Custom Quant Buffet logic — adapt the signal block to match your lab on_day().
# Default: equal-weight. Port your make_on_day weights here via SetHoldings.
w = 1.0 / len(self.symbols) if self.symbols else 0.0
for symbol in self.symbols:
self.SetHoldings(symbol, w)
Exported code uses the platform’s native classes and libraries. Install dependencies in your third-party IDE, then run. Validate before live trading.