spider-strategy
SPIDER v5.1.1 โ Two autonomous style legs on two wallets, one producer. NOT a copy-trader: each leg scores its own universe to a STYLE and pushes signals; the runtime owns the LLM gate (pass-through), DSL exits, and all risk.guard_rails. SWING leg = Tech & AI multi-day momentum on a DYNAMIC XYZ-equity universe (curated semis/AI/space include-set + auto-caught fresh listings like CBRS/Cerebras and SPCX/SpaceX) plus static crypto alts (SUI/ONDO/HYPE/NIL/GRASS/ZEC), LONG only, 4h+1h trend structure + 24h relative-strength, conviction leverage clamped 10x, wide let-winners-run DSL. SCALP leg = Macro & majors fast mean-reversion (BTC/ETH/SOL/HYPE + xyz:BRENTOIL/xyz:CL), BOTH directions, short-TF stretch + RSI extreme with a 1h trend filter, strict 5x, tight fast-capture DSL. SPIDER_LEG env selects the leg.
What this skill does
# ๐ท๏ธ SPIDER v5.0 โ Two-Persona Style Hunter Spider runs **two concurrent strategy wallets**, each a distinct trading style. **One producer script** (`spider-producer.py`) serves both; the `SPIDER_LEG` env var selects which leg a given daemon is. Each leg binds to its own wallet, runtime YAML, DSL, and risk envelope. > **Not a copy-trader.** Earlier Spider versions chased other traders' > books. v5.0 hunts the **style**: each leg scores its own universe with > its own technicals and emits its own signals. The runtime LLM gate is > pass-through; the runtime owns execution + DSL + risk. | Leg | Style | Wallet env | Runtime | Scanner | |---|---|---|---|---| | `swing` | Tech & AI multi-day momentum, LONG only | `SPIDER_SWING_WALLET` | `runtime-swing.yaml` | `spider_swing_signals` | | `scalp` | Macro & majors fast mean-reversion, BOTH dirs | `SPIDER_SCALP_WALLET` | `runtime-scalp.yaml` | `spider_scalp_signals` | ## What changed from v4.0 v4.0 was a single-leg "patient anchor sniper" โ one 7-day LONG scored on arena-leader alignment + SM consensus. v5.0 is a full thesis **replacement**: two style legs, multi-signal baskets, both directions on the scalp leg, and a leg-parameterized producer. The old single-leg `runtime.yaml` / `spider-config.json` are removed. **v5.1** made the swing XYZ-equity universe **dynamic**: instead of a fixed `allowedAssets` list, the leg rebuilds its equity pool each tick from the live instrument board and **auto-catches freshly listed Pre-IPO Perpetuals / AI IPOs** (the edge behind Spider's CBRS/Cerebras win โ a name that did not exist as a tradeable ticker when a static list would have been written). The scalp universe stays static (majors + energy). See the SWING universe section above. --- ## SWING leg โ Tech & AI multi-day momentum (LONG only) Multi-day trend rider. Holds a small basket of the strongest names in a semiconductor/AI + high-beta-alt universe, sits through drawdowns while the multi-timeframe trend holds. **Universe** (`config/spider-swing-config.json`) โ **dynamic**, rebuilt every tick by `build_universe()`: - **Static crypto alts** (`cryptoAlts`): `SUI / ONDO / HYPE / NIL / GRASS / ZEC`. - **Dynamic XYZ equities**: derived from the live `market_list_instruments` board (the same call already made for venue-leverage caps โ zero extra cost). An XYZ name is eligible if it is **liquid** (`dayNtlVlm โฅ xyzVolFloorUsd`, default $5M) **and** either (a) its bare ticker is in the curated tech/AI/space **`xyzIncludeSet`** (`NVDA AMD INTC MRVL MU TSM ASML ARM SMSN SKHX DRAM SNDK DELL LITE CRWV PLTR ORCL GOOGL META MSFT AMZN AAPL NFLX IBM COIN MSTR CRCL HOOD SPCX RKLB CBRS`), or (b) it was **first seen < `xyzFreshDays`** (default 21d) ago **and** is **not** in the commodity/FX/ index **`xyzExcludeSet`**. Branch (b) auto-catches new **Pre-IPO Perpetuals / AI IPOs** (Spider's CBRS/Cerebras and SPCX/SpaceX wins) with no code edit. Qualifiers are capped to the top **`xyzMaxNames`** (default 20) by 24h volume to bound per-tick candle fetches; the score gate below does the final quality filtering. First-seen timestamps live in `state/xyz-first-seen-swing.json`. On first run every current name is back-dated as already-old, so the auto-catch fires only on names that appear **after** deploy. A freshly listed perp needs ~24h of candles (โฅ6 4h bars) before it can score. If the instrument board is unavailable, the leg falls back to a static `allowedAssets` list. ### Scoring (raw integer; `minScore` 5) | Component | Pts | Source | |---|---|---| | 4h trend structure | +3 BULLISH / โ4 BEARISH | `market_get_asset_data` 4h candles | | 1h trend confirmation | +2 BULLISH / โ1 BEARISH | 1h candles | | 24h relative-strength proxy | +3 (โฅ8%) / +2 (โฅ4%) / +1 (โฅ1%) / โ1 (<0) | `markPx` vs `prevDayPx` | | RSI room | +1 (<50) / โ2 (> `rsiMaxLong` 78) | 1h RSI | | Funding | +1 (negative) / โ1 (crowded long) | instrument context | | SM consensus bonus | +2 LONG / โ2 SHORT | `leaderboard_get_markets` (alts only; XYZ has none) | Direction is always LONG โ a bearish 4h structure drives the score below `minScore`, so the leg simply waits. Requires 4h **and** 1h bullish alignment to clear the floor. ### Execution & exit - slots **3**, `margin_pct` **28%** (3 ร 28 = 84% max committed), tick **300s** - conviction leverage clamped **10x**, then to each asset's venue max - DSL **wide let-winners-run**: phase1 max_loss **22%** / retrace 12 / 1 breach; **all time-cuts OFF**; `hard_timeout` **7d** staleness backstop; phase2 ladder `15%โlock0 / 30%โ45 / 60%โ68 / 100%โ80 / 150%โ90` - low turnover: `max_entries_per_day` **12** (raised from 4 โ don't throttle the winning style by trade count; the loss-based gates own risk), `per_asset_cooldown` **4h**, `bypass_max_entries_per_day_on_profit` **true** --- ## SCALP leg โ Macro & majors fast mean-reversion (BOTH directions) Fades short-timeframe stretch and rides the snap-back. Long-biased but actively shorts when overbought. Strict 5x, minutes-to-hour holds, high win rate, small per-trade size. **Universe** (`config/spider-scalp-config.json` โ `allowedAssets`): majors `BTC / ETH / SOL / HYPE` + energy `xyz:BRENTOIL / xyz:CL`. ### Scoring (raw integer; `minScore` 4) Picks the more-extreme side (oversold โ LONG, overbought โ SHORT), then: | Component | Pts | |---|---| | RSI extreme | +3 (โค20 / โฅ80) / +2 (โค25 / โฅ75) / +1 (โค `rsiOversold` 30 / โฅ `rsiOverbought` 70) | | Stretch from 20-bar 15m MA | +2 (โฅ2ร `stretchThresholdPct` 0.8%) / +1 (โฅ1ร) | | 1h trend filter | +1 fading **with** higher-TF bias / โ2 against a strong trend (knife guard) | | Funding tiebreak | +1 (shorts pay a LONG / longs pay a SHORT) | The โ2 knife guard keeps the leg from longing a falling knife or shorting a ripping uptrend โ it only fires on genuine intraday extremes. ### Execution & exit - slots **4**, `margin_pct` **15%** (small scalp size), tick **60s** - **strict 5x** leverage clamp (the style's defining discipline), then venue max - DSL **tight fast-capture**: phase1 max_loss **5%** (tightened from 7% to lose less) / retrace 3 / 1 breach; `weak_peak_cut` **ON** (30m @ 1.5), `dead_weight_cut` **ON** (25m), `hard_timeout` **2h**; phase2 ladder `3%โlock35 / 6%โ55 / 12%โ70 / 25%โ85` - **turnover**: `max_entries_per_day` **18** (trimmed from 30) โ *fee-sensitive*; lower further if net-of-fees underperforms --- ## Leverage clamping (both legs) Desired leverage = the leg cap (`swingMaxLeverage` 10 / `scalpMaxLeverage` 5). The producer then clamps to each asset's **Hyperliquid venue max**, read from `market_list_instruments` โ `instruments[].max_leverage` (one call per tick, whole universe). This prevents emitting an unfillable order โ e.g. `GRASS` and `NIL` cap at **3x**, so a swing 10x desire is clamped to 3x for those names. The runtime decision gate also rejects any leverage above the leg cap as a clamp-breach defense. ## XYZ (HIP-3) asset handling XYZ equities/energy require `dex="xyz"` on `market_get_asset_data` (an empty dex errors with `Asset prefix "xyz" must match dex`). Main-DEX assets pass `dex=""`. The `main` and `xyz` sub-DEX sections are two VIEWS of ONE cross-margined wallet (not two collateral silos), so both report the same `accountValue`. `get_positions()` takes `accountValue` ONCE via `max()` across the two views โ never sums it. Summing double-counts the balance and sizes every position 2x too large (`margin_usd = account_value * margin_pct`). `assetPositions` ARE per-sub-DEX, so those are enumerated across both. Candle fields are HL-native (`o/h/l/c/v`). ## Race-window dedup Each `push_signal(coin)` is recorded in `state/recent-signals-<leg>.json` (per-leg). The producer skips any coin seen within 180s **before** scoring โ covering the gap between a push returning OK and the position appearing in the next-tick clearinghouse pull. On-chain held-asset filtering (`get_positions`) is the safety floor underneath. ## Risk gates (`risk.guard_rails`) | Gate | swing | scalp | |---
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts โ single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score โฅ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.