smithery/neversight

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.

Installation

$ npx skills add smithery/neversight --skill hft-quant-expert

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/neversight · top by installs.

npx skills add smithery/neversight

Browse all from smithery/neversight

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,440 B
  • docs SUMMARY.md 242 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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