Index of every page on this site: llms.txt
All skills
tradermonty avatar

/strategy-pivot-designer

@f95e770
Run it yourself

Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.

Use this Skill: https://skilld.dev/gh/tradermonty/claude-trading-skills/strategy-pivot-designer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈42 tokens for metadata: the name and description. ≈869 when used: this file. ≈5.4k more on demand in 5 files.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈170 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Strategy Pivot Designer

Overview

Detect when a strategy's backtest iteration loop has stalled and propose structurally different strategy architectures. This skill acts as the feedback loop for the Edge pipeline (hint-extractor -> concept-synthesizer -> strategy-designer -> candidate-agent), breaking out of local optima by redesigning the strategy's skeleton rather than tweaking parameters.

When to Use

  • Backtest scores have plateaued despite multiple refinement iterations.
  • A strategy shows signs of overfitting (high in-sample, low robustness).
  • Transaction costs defeat the strategy's thin edge.
  • Tail risk or drawdown exceeds acceptable thresholds.
  • You want to explore fundamentally different strategy architectures for the same market hypothesis.

Prerequisites

  • Python 3.9+
  • PyYAML
  • Iteration history JSON (accumulated backtest-expert evaluations)
  • Source strategy draft YAML (from edge-strategy-designer)

Output

  • pivot_drafts/research_only/*.yaml — strategy_draft compatible YAML proposals
  • pivot_drafts/exportable/*.yaml — export-ready drafts + ticket YAML for candidate-agent
  • pivot_report_*.md — human-readable pivot analysis
  • pivot_manifest_*.json — metadata for all generated files
  • pivot_diagnosis_*.json — stagnation detection results

Workflow

  1. Accumulate backtest evaluation results into an iteration history file using --append-eval.
  2. Run stagnation detection on the history to identify triggers (plateau, overfitting, cost defeat, insufficient profit factor, tail risk). A no-loss profit factor is not cost defeat; an undefined or overflowed ratio requires review.
  3. If the diagnosis says review_required, repair or re-evaluate the underlying metrics first; do not generate pivots. If stagnation is confirmed, generate pivot proposals using three techniques: assumption inversion, archetype switch, objective reframe.
  4. Review ranked proposals (scored by quality potential + novelty).
  5. For exportable proposals, ticket YAML is ready for edge-candidate-agent pipeline.
  6. For research_only proposals, manual strategy design needed before pipeline integration.
  7. Feed the selected pivot draft back into backtest-expert for the next iteration cycle.

Quick Commands

Append a backtest evaluation to history (creates history if new):

python3 skills/strategy-pivot-designer/scripts/detect_stagnation.py \
  --append-eval reports/backtest_eval_2026-02-10_120000.json \
  --history reports/iteration_history.json \
  --strategy-id draft_edge_concept_breakout_behavior_riskon_core \
  --changes "Widened stop_loss from 5% to 7%"

Detect stagnation:

python3 skills/strategy-pivot-designer/scripts/detect_stagnation.py \
  --history reports/iteration_history.json \
  --output-dir reports/

Generate pivot proposals:

python3 skills/strategy-pivot-designer/scripts/generate_pivots.py \
  --diagnosis reports/pivot_diagnosis_*.json \
  --strategy reports/edge_strategy_drafts/draft_*.yaml \
  --max-pivots 3 \
  --output-dir reports/

Resources

  • skills/strategy-pivot-designer/scripts/detect_stagnation.py
  • skills/strategy-pivot-designer/scripts/generate_pivots.py
  • references/stagnation_triggers.md
  • references/strategy_archetypes.md
  • references/pivot_techniques.md
  • references/pivot_proposal_schema.md
  • skills/backtest-expert/scripts/evaluate_backtest.py
  • skills/edge-strategy-designer/scripts/design_strategy_drafts.py

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning8d5 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    The skill is a local toolset for algorithmic trading strategy development. It provides Python scripts to detect stagnation in strategy iterations and suggest structural pivots based on pre-defined archetypes. No malicious patterns, network exfiltration, or credential risks were detected.

  • Socket8d

    No alerts

  • Snyk8d

    Risk: LOW · No issues

  • Runlayer8mo

    4/12 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f95e770. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month

README badge

README badge for tradermonty/claude-trading-skills/strategy-pivot-designer