multi-market-strategy

Generate per-symbol trading signals for cross-market portfolios with volatility-adjusted weighting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you run portfolio signal generation and backtesting when your universe contains symbols from multiple markets, where each market has different trading calendars and volatility characteristics.

Core Features & Use Cases

  • Cross-market signal generation: Detects the market type per symbol (A-share, crypto, US/HK equity, forex, futures) and computes signals with market-specific parameters.
  • Volatility-adjusted allocation: Scales signal strength by inverse volatility so higher-volatility assets (e.g., crypto) do not dominate the risk budget.
  • Calendar and market-rule handling: Relies on the CompositeEngine to align dates, apply per-market rules (e.g., T+1, funding/swap mechanics), and allocate shared capital while this strategy focuses on target signals.

Quick Start

Ask the system to backtest a multi-asset universe like ["000001.SZ", "BTC-USDT"] from 2024-01-01 to 2025-03-31 using the daily engine with auto source loading.

Frequently Asked Questions about multi-market-strategy

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

FAQPage Schema
How do I backtest a cross-market portfolio with different trading calendars?

Cross-market backtesting requires calendar alignment and market-specific execution rules. This strategy relies on the CompositeEngine to align dates and apply per-market rules, while generating per-symbol trading signals for a mixed portfolio spanning different asset classes.

How do I prevent high-volatility assets like crypto from dominating my portfolio allocation?

Portfolio allocation prevents high-volatility assets from dominating by applying volatility-adjusted signal weighting. This strategy scales signal strength by inverse volatility so that higher-volatility assets do not consume an outsized share of the risk budget.

Can I backtest a portfolio combining A-shares and crypto?

You can backtest mixed asset class combinations like A-shares plus crypto. The strategy detects the market type per symbol and computes signals using market-specific parameters to handle the distinct characteristics of each asset class.

What's the best way to generate trading signals for multi-asset portfolios?

Generating trading signals for multi-asset portfolios requires per-market indicator parameterization and volatility adjustment. This strategy detects market types per symbol and applies risk-balanced weights to target signals across different exchanges.

Do I need a specific engine to handle market-specific rules for multi-market backtesting?

Multi-market backtesting requires the CompositeEngine to align trading calendars and apply per-market rules such as T+1 or funding mechanics. This strategy focuses on target signal generation and relies on the engine for execution and capital allocation.

Why do my multi-market backtest signals fail to align across different exchanges?

Multi-market signals fail to align due to differing trading calendars and volatility profiles. This strategy addresses the issue by using the CompositeEngine for date alignment and applying volatility-adjusted signal weighting across the cross-market portfolio.