Receber por email
← Voltar para o catálogo

hft-quant-expert

Quantitative trading expertise for DeFi and crypto derivatives. Use when building trading strategies, signals, risk management. Triggers on signal, backtest, alpha, sharpe, volatility, correlation, position size, risk.

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/hft-quant-expert/svg)](https://www.skillteca.com.br/skills/hft-quant-expert)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

HFT Quant Expert

Quantitative trading expertise for DeFi and crypto derivatives.

When to Use

  • Building trading strategies and signals
  • Implementing risk management
  • Calculating position sizes
  • Backtesting strategies
  • Analyzing volatility and correlations

Workflow

Step 1: Define Signal

Calculate z-score or other entry signal.

Step 2: Size Position

Use Kelly Criterion (0.25x) for position sizing.

Step 3: Validate Backtest

Check for lookahead bias, survivorship bias, overfitting.

Step 4: Account for Costs

Include gas + slippage in profit calculations.

Quick Formulas

# Z-score
zscore = (value - rolling_mean) / rolling_std

# Sharpe (annualized)
sharpe = np.sqrt(252) * returns.mean() / returns.std()

# Kelly fraction (use 0.25x)
kelly = (win_prob * win_loss_ratio - (1 - win_prob)) / win_loss_ratio

# Half-life of mean reversion
half_life = -np.log(2) / lambda_coef

Common Pitfalls

  • Lookahead bias - Using future data
  • Survivorship bias - Only existing assets
  • Overfitting - Too many parameters
  • Ignoring costs - Gas + slippage
  • Wrong annualization - 252 daily, 365*24 hourly
Compartilhar X LinkedIn