Use when writing a high-turnover intraday strategy on Superior Trade — anything described as scalping, momentum bursts, fast in/out, RSI thrust, volume spike entry, 5-minute strategy. Note this template was unprofitable in our reference backtest (33% WR, -0.34%); use it as a structural template, not a recommendation.
npx skills add https://github.com/Superior-Trade/superior-skills --skill scalping
A user asks for a scalping strategy, "fast in/out", "5m strategy", "ride the thrust", "buy when volume spikes". Single-pair, tight stops, time-stopped trades.
The reference backtest below was unprofitable (33% WR, −0.34% PnL, Sharpe −5.6) on SOL 5m over April 2026. The strategy *executes correctly* — it's not broken — it's just a losing parameter set on this window. The 0.6% target / 0.4% stop ratio needs ~41% hit rate to break even before fees, which the entry filter didn't deliver. Do not deploy as-is. Tune the entry threshold and validate before recommending to a user.
This skill exists as a structural template for high-turnover momentum entries. Real edge requires parameter search, regime filtering, or a different signal.
| Window | SOL/USDC:USDC 5m, 2026-04-01 → 2026-05-01 (30 days) |
|---|---|
| Trades | 76 |
| Win rate | 33% |
| Wallet PnL | −0.34% |
| Sharpe | −5.6 |
| Backtest ID | 01kqypvbmjjhqjn3ae8bgqr9p0 |
from freqtrade.strategy import IStrategy
from datetime import datetime
import pandas as pd
import talib.abstract as ta
class SolScalpMomentumStrategy(IStrategy):
minimal_roi = {"0": 0.006} # 0.6% profit target
stoploss = -0.004 # 0.4% stop
trailing_stop = False
timeframe = "5m"
process_only_new_candles = True
startup_candle_count = 100
can_short = False
def populate_indicators(self, dataframe: pd.DataFrame, metadata: dict) -> pd.DataFrame:
# Session VWAP approximation over the last 288 bars (~24h).
tp = (dataframe["high"] + dataframe["low"] + dataframe["close"]) / 3.0
pv = tp * dataframe["volume"]
dataframe["vwap"] = pv.rolling(288).sum() / dataframe["volume"].rolling(288).sum()
dataframe["rsi"] = ta.RSI(dataframe, timeperiod=14)
dataframe["vol_avg20"] = dataframe["volume"].rolling(20).mean()
dataframe["vol_thrust"] = dataframe["volume"] / dataframe["vol_avg20"]
return dataframe
def populate_entry_trend(self, dataframe: pd.DataFrame, metadata: dict) -> pd.DataFrame:
dataframe.loc[
(dataframe["close"] > dataframe["vwap"])
& (dataframe["rsi"] > 70)
& (dataframe["vol_thrust"] > 2.0),
"enter_long",
] = 1
return dataframe
def populate_exit_trend(self, dataframe: pd.DataFrame, metadata: dict) -> pd.DataFrame:
dataframe.loc[(dataframe["rsi"] < 50), "exit_long"] = 1
return dataframe
def custom_exit(self, pair: str, trade, current_time: datetime,
current_rate: float, current_profit: float, **kwargs):
# Time stop at 12 minutes (~3 bars on 5m).
elapsed = (current_time - trade.open_date_utc).total_seconds()
if elapsed >= 12 * 60:
return "time_stop_12m"
return None
{
"exchange": { "name": "hyperliquid", "pair_whitelist": ["SOL/USDC:USDC"] },
"stake_currency": "USDC",
"stake_amount": 100,
"timeframe": "5m",
"max_open_trades": 1,
"stoploss": -0.004,
"minimal_roi": { "0": 0.006 },
"trading_mode": "futures",
"margin_mode": "cross",
"entry_pricing": { "price_side": "same" },
"exit_pricing": { "price_side": "same" },
"pairlists": [{ "method": "StaticPairList" }]
}
| Knob | Effect |
|---|---|
| rsi > 70 | Stricter (> 80) → fewer entries, only the strongest thrusts. |
| vol_thrust > 2.0 | Tighter (> 3.0) → only volume blowouts; very rare. |
| 0.006 ROI | Wider target → more time in trade, more tail risk. |
| 0.004 stop | Tighter stop → more stops out, lower per-trade loss. |
| 12 * 60 time stop | Faster timeout → more trades but lower edge per trade. |
Three structural issues in the reference parameters:
rsi < 30 + vol_thrust > 2.0) for a fade entry is worth testing.VolumePairList increases hit count, lets the law of large numbers help.Practical refinements before suggesting to a user:
1h close > 1h ema_50).fees-optimizations.startup_candle_count too low. The 288-bar VWAP needs 288 bars of warmup; default 30 produces NaN VWAP for the first 24h.docs/standard-strategies-audit.md, backtest 01kqypvbmjjhqjn3ae8bgqr9p0fees-optimizations for fee-aware sizing of tight-target strategies.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take superior-trade/scalping from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.